<?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 Haytham Elkhoja on Medium]]></title>
        <description><![CDATA[Stories by Haytham Elkhoja on Medium]]></description>
        <link>https://medium.com/@haythamelkhoja?source=rss-ad66a1cb0000------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*VjETniLMLdjx_PrF75IaHg.png</url>
            <title>Stories by Haytham Elkhoja on Medium</title>
            <link>https://medium.com/@haythamelkhoja?source=rss-ad66a1cb0000------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:39:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@haythamelkhoja/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[Securing your Kubernetes Deployment]]></title>
            <link>https://medium.com/ibm-cloud/securing-your-kubernetes-deployment-fb9f0d823fc?source=rss-ad66a1cb0000------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb9f0d823fc</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Haytham Elkhoja]]></dc:creator>
            <pubDate>Wed, 10 Apr 2019 20:18:19 GMT</pubDate>
            <atom:updated>2019-04-22T20:36:22.075Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Written by </em><a href="https://medium.com/@chandnivaya"><em>Chandni Vaya</em></a><em>. Peer reviewed and contribution by </em><a href="https://medium.com/@haythamelkhoja"><em>Haytham Elkhoja</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*EEeLZB3F8tdoJNBoa8ulqQ.png" /></figure><p>In case you haven’t heard, Kubernetes is a big deal. It allows orchestrating the deployment and lifecycle of your applications running on containers.</p><p>Security is always a point of concern when adopting new platforms and technologies. Here, we try to shed the light on some of the best practices and things to be aware of using Kube for your modern distributed app.</p><p>And depending on what Kubernetes platform you’re using, a cloud-based managed Kubernetes service like <a href="https://www.ibm.com/cloud/container-service">IBM Cloud Kubernetes Service</a>, Amazon EKS, Microsoft AKS or Google GCP, or an on-prem Kubernetes solution such as <a href="https://www.ibm.com/cloud/private">IBM Cloud Private</a>, Red Hat OpenShift Container Platform, Pivotal Kubernetes Service or Rancher, developers, SREs and sysadmins alike should be aware of the different attack vectors of a Kube architecture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dORfPJr3F6mfHkc485eHQA.png" /><figcaption>Kubernetes Attack Surface</figcaption></figure><h3>Kubernetes Attack Vectors</h3><p>Attack vectors are means or gates by which malicious users will try to crack the armor and attack your platform in the following areas:</p><ol><li>Container Images</li><li>Platform and Worker Nodes</li><li>Communication</li></ol><h4>1. Container Images</h4><p>The app (or container image) is where developers will eventually have the most control over security. And nothing changes much in terms of application development when applying security best practices.</p><p>But Docker images are made out of base images and tens of layers that are built by third-parties, developers need to feel confident in the authenticity and security of the container images layers. Organizations, on the other hand, need to enforce compliance rules and proper processes when re-using third-party base images.</p><p>For example, a normal Java application needs JDK as a base image, which in turn needs a base OS image that could have security vulnerabilities, or that certain version of JDK base image might not be vetted by the organization for production usage.</p><p>Thankfully, many tools can help you assess the security of your base images and enforce compliance rules. <a href="https://cloud.ibm.com/docs/services/va?topic=va-va_index#about">IBM Vulnerability Advisor</a> and open-source tools such as Twistlock, CoreOS Clair, Dagda, Anchore, etc… continuously test your image for possible vulnerabilities and alert you when developers are not using proper base images.</p><p>Other best practices when building your Docker images:</p><ul><li>Practice the principle of least privilege — <strong>do not</strong> give your application any type of root access.</li><li>Go for minimal and official base images — more often than not — the open source community or vendors publish usable and signed minimal official images that should be verified to avoid MITM attacks. Make it a habit to <strong>verify</strong> images as you pull them by using:</li></ul><pre>export DOCKER_CONTENT_TRUST=1</pre><ul><li>Keep your Docker file and image clean of sensitive information— this means <strong>never </strong>including tokens, IP addresses, user/passwords etc.. Bootstrap them when running instead.</li></ul><h4>2. Platform and Worker Nodes</h4><p>Now depending on the solution you’re using, you might or might not have access to any of the nodes. If you do have admin privilege on the worker nodes or are deploying an on-prem Kube solutions, then you should consult your vendor documentation on security best practices. For example, IBM’s Cloud Private has <a href="https://www.ibm.com/support/knowledgecenter/en/SSBS6K_3.1.2/user_management/admin.html">guidelines</a> on hardening and securing IBM Cloud Private for production. There are also <a href="https://public.dhe.ibm.com/common/ssi/ecm/59/en/59022659usen/59022659usen-01_59022659USEN.pdf">guides</a> to follow to comply with PCI DSS. Red Hat’s OpenShift Container Platform has also published <a href="https://docs.openshift.com/container-platform/3.7/security/securing_container_platform.html">documentation</a> on how to harden and secure it.</p><p>Here are some best practices on securing your Kubernetes platform:</p><ul><li>There are plenty of OS security hardening articles online and benchmarks from organizations like <a href="https://www.cisecurity.org/benchmark/kubernetes/">CIS</a> (Center of Internet Security) that guide administrators and security staff on how to secure their environments.</li><li>Harden your <a href="https://docs.docker.com/engine/security/security/">Docker</a> Engine or containerD runtime. containerD is still relatively new (as of April 2019), but is quickly replacing Docker engine as main runtime in many on-prem Kube solutions.</li><li>Encrypt the worker nodes file system with solutions like <a href="https://guardianproject.info/code/luks/">LUKS</a> or <a href="https://gitlab.com/cryptsetup/cryptsetup/wikis/DMCrypt">dm-crypt</a>.</li><li>In-memory encryption and the use of runtimes enclaves is growing amongst cloud providers alongside encryption at rest and in motion. You may have heard of <a href="https://fortanix.com/">Fortanix</a> or <a href="https://sconecontainers.github.io/">Scone</a>, which are some of the solutions that rely on <a href="https://software.intel.com/en-us/sgx">Intel SGX</a> to make that magic happen.</li><li>Enable secrets data encryption by using Key Management Service (KMS) providers and plugins. Most on-prem solutions have plugins and documentation to integrate HashiCorp’s <a href="https://www.vaultproject.io/">Vault</a> for example.</li><li>Authentication and access control policies become an issue when many users are sharing a cluster. Most Kubernetes can plugin to off-the-shelf Identity and Access Management tools (IAM) for Role Based Access Control (RBAC) and fine-graining control base on namespaces for example.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KhFWvEdNmC7IquWvoO1Nlw.png" /><figcaption>Role-Based Access Control in Kubernetes</figcaption></figure><h4>3. Communication</h4><p>If you’re on Kubernetes that means that you’re deploying distributed systems and unlike monolithic applications that rely on in-process messages, in a microservices world, messages use the network.</p><p>Before we dive in securing communication on Kubernetes we have to differentiate two things: <strong>Control-plane</strong> and <strong>Data-plane</strong>.</p><p><strong>Control-plane</strong> communication is basically all the traffic that goes between Kubernetes cluster management daemons and the Kubernetes API Server and that’s normally secured via HTTPS.</p><p>At its simplest form, encrypting all communication traffic within the cluster should be a non-brainer. Both <a href="https://www.ibm.com/support/knowledgecenter/en/SSBS6K_3.1.2/installing/fips_encrypt_com.html">IBM Cloud Private</a> and <a href="https://docs.openshift.com/container-platform/3.11/admin_guide/ipsec.html">Red Hat OpenShift Container Platform</a> provide documentation to enable end to end IPSec between hosts.</p><p>However, one thing to note here is that all Kubernetes control-plane communication normally passes through HTTPS, so using IPSec encrypts traffic a second time could be seen as overhead in some situations but valuable for FIPS compliance for example.</p><p><strong>Data-plane</strong> communication is basically all the traffic that goes between pods and services that host the containers. Now, you could manually deploy SSL certificates in Ingress rules and that’s fine, but also tiresome.</p><p>The alternative would be to automate that process using Mutual TLS from <a href="https://www.istio.io/">Istio</a>. While Istio is a service mesh and much more than simply an encryption tool, Istio’s mTLS guarantees that communication between services created for a deployment are encrypted. Istio makes it that clients and servers verify the authenticity of the certificates in both directions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Rw8J2jQTwFyIhXmGzuP_A.jpeg" /><figcaption><a href="https://www.infoq.com/presentations/istio-service-mesh">https://www.infoq.com/presentations/istio-service-mesh</a></figcaption></figure><p>When talking about <strong>Data-planes</strong>, Kubernetes allows you to micro-segment and assign policies to how pods talk to each other and to other nodes within a cluster. By default, pods are non-isolated as in they accept traffic from any source which is problematic in a shared environment or when deploying multiple applications in a single cluster.</p><p>NetworkPolicies aren’t native to Kubernetes, they are however applied by a running Software-Defined Networking component such as Calico, OVS or VMware NSX-t.</p><p>Above are some of the important security measures that should be taken into consideration without fail because be certain that security attacks are imminent and security shouldn’t be an after-thought, but a primary concern when modernizing your app.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb9f0d823fc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ibm-cloud/securing-your-kubernetes-deployment-fb9f0d823fc">Securing your Kubernetes Deployment</a> was originally published in <a href="https://medium.com/ibm-cloud">IBM Cloud</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IBM Cloud Automation Manager, a primer.]]></title>
            <link>https://medium.com/ibm-cloud/ibm-cloud-automation-manager-a-primer-460d912246d2?source=rss-ad66a1cb0000------2</link>
            <guid isPermaLink="false">https://medium.com/p/460d912246d2</guid>
            <category><![CDATA[cloud-automation-manager]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[chefs]]></category>
            <dc:creator><![CDATA[Haytham Elkhoja]]></dc:creator>
            <pubDate>Tue, 28 Aug 2018 19:29:05 GMT</pubDate>
            <atom:updated>2018-09-10T18:49:16.742Z</atom:updated>
            <content:encoded><![CDATA[<p>The development community is adopting containers at a remarkably breakneck pace. Organizations are looking to containerize their workloads for different reasons. Whether it’s the packaging advantage of containers, their smaller size (compared to VMs), or their ‘<em>build once, run anywhere’</em> attribute, the main motivation that is commonly shared across individuals and organizations alike — the agility and ephemeral nature of containers.</p><p>But with all of their benefits, enterprises consider containers to be bleeding edge, and are cautiously (and curiously) accepting the reality that the world is adopting hybrid architectures composed of containers and VMs that work side-by-side in multi-cloud platforms. This “new world order” of containers + VMs isn’t without its challenges and complexities when dealing with operations and workload management.</p><p>To this intention, and while it is industry-wide agreed that VMs (and infrastructure in general) are here to stay for the foreseeable future, this made some very smart people think of ways to bring some qualities of the container world to VMs. Welcome to the exciting world of <em>Infrastructure as Code (IaC).</em></p><p>In this article, I introduce IBM Cloud Automation Manager, an enterprise-ready Infrastructure as Code (IaC) platform that provides a single pane of glass to provision VM-based alongside Kubernetes-based workloads by simply using templates (text files).</p><h4>IBM Cloud Automation Manager</h4><p>IBM Cloud Automation Manager (or CAM for short) was released late 2017 alongside IBM Cloud Private, IBM’s enterprise-grade Kubernetes platform. Simply put, CAM is an enterprise-ready Infrastructure as Code (IaC) manager that allows you to:</p><ul><li>Automate the provisioning of workloads, whether virtual machines and/or containers and their infrastructure pre-requisites.</li><li>Compose and orchestrate services made out of both VMs and containers.</li><li>Integrate multiple Infrastructure as Code and Configuration Manager solutions.</li><li>Provision workloads on multiple clouds (whether public or private).</li><li>Integrate with DevOps toolchains.</li><li>Integrate with day-2 ITSM solutions.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dQYluGw3CE9O2OpBzWDPtg.png" /></figure><p>As seen in the diagram above, IBM Cloud Automation Manager has 3 main user-visible components:</p><ol><li><strong>Terraform,</strong> which handles the provisioning of cloud and infrastructure resources using providers such as VMware vSphere, Microsoft Azure, IBM Cloud Platform, Amazon Web Services, Google Cloud Platform and even OpenStack.</li><li><strong>Chef,</strong> which does configuration management and compliance automation. Chef normally takes over the provisioning after <strong>Terraform</strong> to start deployment and configuration of middleware and applications.</li><li><strong>Service Composer,</strong> which is where administrators can author, compose and design services that are made out of not only multiple VMs, but also Kubernetes resources by invoking <strong>Helm </strong>charts.</li></ol><p>Take this scenario for example: A common practice is to have front-end apps deployed on containers and databases (or legacy middleware) deployed on VMs, and to take things up a notch, containers might be living on a public cloud while databases might reside behind an enterprise firewall.</p><p>Service Composer helps organizations create hybrid workloads of containers, public cloud resources, and on-premise VMs with the click of a button. This simplicity comes in handy at the end of the DevOps toolchain, when environments need to be deployed on demand for Dev, Test, QA and then Production.</p><p>In simple terms, with IBM Cloud Automation Manager, administrators and developers alike are able to <strong>define</strong> where and how target environments should look like, author <strong>declarative </strong>code, save and then <strong>version</strong> to Git. And because environments are written as declarative templates, they can be <strong>re-produced and re-deployed over and over.</strong></p><h4>What does it solve?</h4><p>Well, many things. First of all, administrators can <strong>automate</strong> most (if not all) of the processes that come with provisioning environments, avoiding manual processes that are tedious and error prone.</p><p>With CAM and Terraform, administrators have to simply declare how they want the environment to look, launch the provisioning, and forget all about it. Terraform will figure out how to deploy.</p><p>See the following image, which displays a typical deployment procedure:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eiCwdmtDG52y7Kb_lpdJeA.png" /></figure><p>Imagine having an application made out of 10 VMs and then having to repeat these steps for each and every environment in a typical enterprise scenario: Dev, QA, UAT, Production and DR, that’s roughly a total of 50 VMs…</p><p>CAM’s automation reduces provisioning time from weeks to hours (dare I say minutes?).</p><p>Second, it solves the issue of <strong>configuration drifts</strong>. Gone are the days when applications don’t behave uniformly when the environments they sit on are <em>supposedly</em> identical. Configuration drifts happen when somebody, somewhere messed up and never reflected the config change to rest of the environments. This happens quite often in a typical Dev, QA, UAT, Production and DR deployment scenario.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*l0vxPp5JQuAUAlTcQqRZsA.png" /></figure><p>And because Terraform templates are text files that are stored in Git, it simplifies integration into existing DevOps tools (such as Jenkins) to help automate the dev-test-prod promotion alongside the application.</p><p>Third, just like application code, infrastructure should be <strong>versioned</strong>. Infrastructure encompasses everything in a software-defined environment, so in the example of VMware we’re talking, amongst other things, Storage I/O Control, Admission Control, vSwitch config, Port Groups, HA Affinity rules, OS customizations (think sysprep), core count, and also sometimes the type of CPU the VM is emulating to enable and disable processor features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*BRhHqOrFLMXwV1qiKghxfQ.png" /></figure><p>Infrastructure doesn’t stop there, it also includes /etc/hosts files, IP configuration, DNS entries, iptables rules, apt-get/yum repos and then, perhaps, middleware configuration might also be part of the responsibility of the infrastructure team, depending on the organization structure.</p><p>Tracking and versioning all aspects of an environment while consolidating VM and container artifacts allow configurations to be branched, forked, rolled-back and then promoted from Dev, QA, UAT, and then Production alongside every other element in an app development delivery process.</p><p>Fourth, Infrastructure as Code allows Ops to <strong>rebuild instead of fixing</strong> when things go wrong. It has been proven time and again that rebuilding an entire environment and then rolling back to a known working version will save time and effort helping achieving SLOs and SLAs.</p><p>Finally, it <strong>saves on disk space</strong>. Currently, organizations rely on VM templates, VM snapshots and a spaghetti of VM clones to quickly provision environments. This is an operational nightmare and wastes disk space, which incidentally opened the doors for storage appliance companies to introduce expensive deduplication technologies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7FjVEvp8ExQkzCHqRoUQOA.png" /></figure><p>Infrastructure as Code allows for replacing clones of VM images with text files that store descriptive declarative statement that reflect configurations and end targets.</p><h3>IBM Cloud Automation Manager Concepts</h3><p>Before digging into CAM, there are some concepts that need to be explained.</p><p><strong>IBM Cloud Private: </strong>IBM Cloud Automation Manager is a Dockerized application that runs on top of IBM Cloud Private, the documentation on how to deploy it can be found <a href="https://www.ibm.com/support/knowledgecenter/en/SS2L37_2.1.0.3/kc_welcome.html">here</a>. Although available on DockerHub, CAM is tightly integrated with IBM Cloud Private as its Kubernetes platform for authorization, RBAC and others functions.</p><p><strong>Git</strong>: Although Git isn’t bundled as part of CAM, it is highly recommended that all the templates and content libraries that are created are stored and versioned on a Git repo. This is also a pre-requisites for air-gapped environments that can’t reach github.com where IBM stores its sample templates.</p><p><strong>Terraform</strong>: By default, IBM Cloud Automation Manager only manages Terraform. Terraform is the module within CAM that talks to and provisions infrastructure. CAM comes with a bunch of Terraform Providers pre-packaged such as: IBM Cloud, AWS, Azure, GCP and OpenStack and the list is growing. Bringing-Your-Own-Provider (BYOP) can be done by following this <a href="https://www.ibm.com/support/knowledgecenter/en/SS2L37_2.1.0.3/cam_using_BYO_terraform.html">link</a>. Terraform has dozens of providers for different types of clouds and infrastructure which can be found <a href="https://www.terraform.io/docs/providers/">here</a>.</p><p><strong>Chef: </strong>Chef is a configuration management tool responsible to deploy and configure simple and complex software from templates (also called cookbooks). There are cookbooks for thousands applications from major software vendors available from <a href="http://supermarket.chef.io/">http://supermarket.chef.io</a>.</p><blockquote>Note: Terraform and Chef overlap in some situations, IBM Cloud Automation Manager takes care of segregating responsibilities, where Terraform will mostly do infrastructure and Chef will mostly do configuration and software deployment.</blockquote><p><strong>CAM Content Provider (or CAMC Provider): </strong>After Terraform completes the provisioning of the VM and if a Chef template is chosen as part of the deployment, CAM engage the CAMC Provider. The CAMC Provider is nothing more than an gateway to a Chef server that takes care of configuration management, middleware and application deployment.</p><p>There are few things to note here:</p><ol><li>The CAMC Provider isn’t installed as part of the CAM installation by default, it’s an optional step that should be executed within CAM. This basically installs a Chef Server on a separate VM.</li><li>The standard Chef that comes with CAMC is pre-populated with some Chef cookbooks also referred to as ‘Pre-Built Content’ covering mostly IBM Oracle and LAMP cookbooks. It is however, the responsibility of administrators to populate other cookbooks from the thousands of cookbooks available on <a href="https://supermarket.chef.io/">Chef Supermarket</a> onto the Chef server and this can be done with Chef’s client: <strong>knife.</strong> Follow this <a href="https://www.ibm.com/support/knowledgecenter/SS2L37_2.1.0.3/content/cam_content_runtime_knife.html">link</a> to understand how to properly manage Chef.</li><li>Although CAM will deploy Chef by default, organizations can choose another configuration manager such as Ansible, Puppet or even their own existing Chef servers. What’s powerful here is that within CAM, organizations can deploy multiple CAMC Providers and multiple configuration managers. For a tutorial on deploying Ansible instead of or alongside Chef, follow this <a href="https://developer.ibm.com/cloudautomation/tutorials/ansible-playbooks/">link</a>.</li></ol><p><strong>Helm: </strong>Helm charts are to Kubernetes what Terraform templates are to VMs. They also are a type of Infrastructure as Code that allow authoring of Kubernetes resources such as deployments, services, replica sets, stateful sets, volumes, ingress rules etc… With Helm charts, developers can package container information and Kubernetes resources as templates, version them and deploy them on-demand, while avoiding the tedious tasks of managing the Kubernetes aspect of things.</p><p><strong>Software Repository:</strong> This is where software binaries will be residing. Normally this should be an NFS share that has ample capacity to store large binaries such as IBM WebSphere, Oracle, Apache, MySQL and other software. This is important for packages that are not publicly accessible, not available on a public repo such as via apt-get/yum or if CAM is residing in an air-gapped environment (with no internet connectivity).</p><p>Administrators should populate the Software Repository with binaries based on a directory structure, to do that, follow the link <a href="https://www.ibm.com/support/knowledgecenter/SS2L37_2.1.0.3/content/cam_installing_imrepo.html">here</a>. For IBM specific software, I highly recommend using PUCL to prepare the software repo, follow this <a href="https://www.ibm.com/support/knowledgecenter/SS2L37_2.1.0.3/content/cam_populating_imrepo_live.html">link</a>.</p><p>Following is a diagram that describes how CAM, Terraform and Chef come together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J8IddDA5maiCLG8KTt8gBw.png" /></figure><p><strong>Templates Library:</strong> A template is nothing more than a Terraform template that declares a VM (or other cloud resources) based on some specifications. All information about the VM such as CPU, disk size, cloud provider is defined there. The Template Library lists all the available templates that are available for provisioning. This is where administrators will spend time creating, authoring and editing Terraform templates.</p><p><strong>Service Library: </strong>A service is a collection of templates executed as one process. IBM Cloud Automation Manager can chain the provisioning and creation of CAM Templates and ICP Helm charts while providing the possibility to pre-set variables and composable execution plans. At the time of writing (CAM 2.1.0.3), provisioning of templates within a service is sequential, however optional parallelism is on the roadmap. What’s more is that within the Service Library, the output parameters from one template can be used as an input to another.</p><p>Service Library is where administrators will spend time creating, authoring, editing and then publishing CAM services to the Service Library.</p><p><strong>Service Composer: </strong>Within the Service Library resides the Service Composer.<strong> </strong>This is CAM’s management console that allows authoring of CAM Services. After the creation of CAM templates (Terraform), administrators can head to the Service Composition section of the Service Library to drag and drop the created CAM templates and/or Kubernetes Helm charts (from IBM Cloud Private) based on a decided sequence and/or decision. Service Composition can also call REST APIs for third party integration and send emails.</p><p><strong>Decision: </strong>A Decision is simply a prompt that a CAM user will face during the provisioning of a service. For example, the service could prompt the user for the size of the VM or whether the workload should be deployed on a Dev or Production environment. During the creation of the service, administrators can choose different CAM templates for each environment. Alternatively, administrators could potentially use Docker versions of certain software for Dev and Test, but then deploy VM based versions for Production.</p><p>A REST hook is a powerful tool that allows CAM to <strong>tell something to do something</strong>. For example, using REST hooks, CAM can plug-in onto an IPAM to request and fetch IP addresses that can be used as parameters (more on that later). REST hooks could also register the newly created service or template to a Change Management Database (CMDB).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9EVZMClkyA58rw6Dkn8eiQ.png" /></figure><p><strong>Parameters and Shared Parameters:</strong> One of the powerful features of CAM are Parameters and Shared Parameters.</p><p>Parameters are data that can be fed onto CAM templates. Things like CPU cores, RAM size, OS could be parameterized and not hard coded within the CAM templates. This is important as it brings modularity and flexibility. CAM templates authors could also choose to prompt users for these parameters or pre-set them during the creation of the templates. One good example of parameters are OS passwords and private ssh keys, no one wants to see those hard coded in templates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*f22A75Y3RI-aMi6nlCCpqg.png" /></figure><p>The image above depicts how Terraform consumes parameters so they are not hard coded onto the CAM templates.</p><p>For example, <em>$(var.folder), $(var.name), $(var.cpu), and $(var.ipv4_prefix_length) </em>are parameters that can be prompted and populated during VM creation or centrally stored within CAM for modularity and do-it-once purposes.</p><p>Parameters are bound to single templates. So what happens when CAM templates need to share certain parameters? Enter Shared Parameters. Shared Parameters allow administrators to parameterize certain data that repeat amongst CAM templates. For example, in an Azure, IBM Cloud or AWS scenario, CAM templates might require the name/ID of the cloud region, which normally don’t change often. Cloud regions such as: <em>us-east-1, eu-central-1, eu-west-1</em> could be shared parameters and used across multiple templates.</p><p>Another example of Shared Parameters usage in VMware Clusters: Imagine having multiple VMware Clusters within an organization and each clusters have different preset settings such as port groups, datastores, or IP gateways. Shared parameters bring sanity and organization to deployments.</p><p>Parameters and Shared Parameters are even more powerful when combined with Decisions as each decision could point to different parameters and shared parameters.</p><p>The concept of Shared Parameters promotes role separation, a cloud admin can be in charge of managing these and choose what parameters should be preset and which can be fiddled or selected by the cloud user/consumer.</p><p>Spend some time watching this video titled, <a href="https://www.youtube.com/watch?v=RtjtmjxsL5g">IBM Cloud Private to deploy IBM Cloud Kubernetes Service Clusters</a>, which shows how almost all the features I covered in this article come together.</p><h3>A day in the life</h3><p>We’ve covered the basics of IBM Cloud Automation Manager and explained the different moving parts that make up CAM. Below is a brief description of what CAM administrators will face day in day out managing CAM.</p><h4>A day in the life of a CAM Administrator</h4><p>Normally, CAM administrators need to worry about the following:</p><ol><li>IBM Cloud Private and IBM Cloud Automation Manager alignment (namespaces, persistent volumes, node selectors, NFS shares, LDAP and RBAC etc..).</li><li>Cloud providers, whether these are VMware vSphere clusters, OpenStack environments or public clouds such as AWS, Azure, GCP, IBM Cloud or even Bring-Your-Own-Provider.</li><li>Centralized repository on Git to store, manage, fork and version Terraform and Chef templates.</li><li>Content publishing, which involves managing, building and then publishing CAM content. CAM content are simply CAM templates (Terraform or Terraform+Chef).</li><li>Service publishing of CAM templates or CAM templates+IBM Cloud Private Helm charts by composing services that consume parameters, request decisions, prompt users for information and integrate with 3rd party tools and platform using REST hooks.</li><li><strong>In the case of private clouds (VMware and OpenStack) </strong>Preparation of OS templates. CAM administrators should be responsible for building and maintaining OS templates that will be used during provisioning of workloads. For example, in the case of Linux, configuration of <a href="https://cloud-init.io/">cloud-init</a>, Logical Volume Manager, apt-get/yum repos etc.. for Windows, things like sysprep, Windows Updates, Windows Features and Active Directory should be accommodated for and thought through.</li><li><strong>In the case of private clouds (VMware and OpenStack)</strong> Preparation of Networking and IP subnets. CAM administrators should have worked out a list of valid IP subnets, vSwitches, port groups, floating IPs, DNS and gateways that can be used in CAM.</li><li><strong>In the case of private clouds (VMware and OpenStack)</strong> Preparation of Storage. CAM administrators should know about storage tiers and datastores available for VMs.</li></ol><h4>A day in the life of a CAM User/Consumer</h4><p>CAM users will eventually consume the templates and services built by CAM Administrators, this means:</p><ol><li>CAM users will be greeted with a template library and a service library where they can browse versions of templates and services already provisioned for them by the CAM administrators.</li><li>Template libraries are where users will execute distinct provisioning.</li><li>Service libraries are where users will execute services made out of multiple templates.</li><li>CAM users will also be able to manage the workloads that they have provisioned. Examples of such actions are (Start, Stop, Pause, Destroy, Delete resources).</li><li>If the CAM user is a developer or part of the DevOps team, then such executions of templates and services can be easily integrated to their DevOps tool chain. By using the CAM API, developers can call the provisioning of templates and services from within Jenkins or any other deployment tool.</li></ol><h3>Conclusion</h3><p>Of course, there are far more features that I haven’t covered such as the ability to integrate CAM workloads with IBM Cloud Private’s ELK, as seen <a href="https://developer.ibm.com/cloudautomation/tutorials/processing-logs-cloud-automation-manager/">here</a>, how to use CAM’s template designer to author Terraform templates without learning Terraform syntax as seen <a href="https://developer.ibm.com/cloudautomation/tutorials/end-end-scenario-shared-parameters-cloud-automation-manager/">here</a> or even how to use CAM’s API to call the service composer from a third party orchestration tool as seen <a href="https://www.ibm.com/support/knowledgecenter/en/SS2L37_2.1.0.3/cam_APIs.html">here</a>.</p><p>In conclusion, IBM Cloud Automation Manager is meant for infrastructure departments who crave the agility and speed experienced when using Docker and Kubernetes (such as with IBM Cloud Private) and want to bring these capabilities to infrastructure and VMs.</p><p>For more information please consult the following links:</p><ul><li><a href="https://developer.ibm.com/cloudautomation/">https://developer.ibm.com/cloudautomation</a></li><li><a href="https://developer.ibm.com/cloudautomation/cloudautomation/new-to/">https://developer.ibm.com/cloudautomation/cloudautomation/new-to/</a></li><li><a href="https://developer.ibm.com/cloudautomation/videos/">https://developer.ibm.com/cloudautomation/videos/</a></li><li><a href="https://www.ibm.com/support/knowledgecenter/en/SS2L37/product_welcome_cloud_automation_manager.html">https://www.ibm.com/support/knowledgecenter/en/SS2L37/product_welcome_cloud_automation_manager.html</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=460d912246d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ibm-cloud/ibm-cloud-automation-manager-a-primer-460d912246d2">IBM Cloud Automation Manager, a primer.</a> was originally published in <a href="https://medium.com/ibm-cloud">IBM Cloud</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IBM Cloud Private Installation Behind a Proxy]]></title>
            <link>https://medium.com/ibm-cloud/ibm-cloud-private-behind-a-proxy-633d6e66021?source=rss-ad66a1cb0000------2</link>
            <guid isPermaLink="false">https://medium.com/p/633d6e66021</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[helm]]></category>
            <category><![CDATA[ibm-cloud-private]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[proxy]]></category>
            <dc:creator><![CDATA[Haytham Elkhoja]]></dc:creator>
            <pubDate>Thu, 03 May 2018 17:10:13 GMT</pubDate>
            <atom:updated>2018-10-01T17:56:19.005Z</atom:updated>
            <content:encoded><![CDATA[<p>Following our last post, <a href="https://medium.com/ibm-cloud/ibm-cloud-private-offline-installation-eb730ae13bfc">IBM Cloud Private Offline Installation,</a> we had many questions around how to deploy and make <a href="https://www.ibm.com/cloud/private">IBM Cloud Private</a> work behind a restrictive HTTP Proxy.</p><p>The main issue is how to let Docker work behind a proxy server during a docker pull. The other issue is around Helm tiller and making it work behind a proxy to populate the App Catalog.</p><p><em>Note 1: If you’ve already deployed IBM Cloud Private and want to configure proxy settings post-installation, jump to the end of this article.</em></p><p><em>Note 2: This article has been updated for IBM Cloud Private 2.1.0.3</em></p><h3>Goal:</h3><ul><li>Demonstrate how to install and deploy IBM Cloud Private behind a proxy, which is very common in an enterprise environment.</li></ul><h3>Assumptions and guidance:</h3><ul><li>You have a common understanding of IBM Cloud Private. Please review the <a href="https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.2/getting_started/introduction.html">overview</a>, <a href="https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.2/getting_started/architecture.html">architecture</a> and <a href="https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.2/getting_started/components.html">components</a> sections of the IBM Cloud Private documentation in IBM Knowledge Center.</li><li>You’re on Red Hat Enterprise Linux 7.4 and IBM Cloud Private 2.1.0.2 or 2.1.0.3.</li><li>You are a root user. If not, all operations in this article should performed by a privileged user by prepending all commands with sudo.</li><li>Remember to verify the target of each command in the command line prompt. Some commands need to be applied on all nodes, others on the boot node.</li></ul><h3>IBM Cloud Private HTTP Proxy Configuration</h3><p>The steps below need to be applied during installation directly after <a href="https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.2/installing/install_docker.html">installation of Docker</a>.</p><p><strong>1. Create the </strong><strong>docker.service.d/ folder</strong></p><p>On all nodes (Master, Management, Proxy and Work nodes), perform the following commands:</p><pre>user@allnodes.icp:~$ sudo mkdir -p /etc/systemd/system/docker.service.d</pre><p>Create the docker.service.d/http-proxy.conf file and add the following variables: HTTP_PROXY, HTTPS_PROXY and NO_PROXY.</p><pre>user@allnodes.icp:~$ sudo vi /etc/systemd/system/docker.service.d/http-proxy.conf</pre><pre>[Service]<br>Environment=&quot;HTTP_PROXY=http://1.2.3.4:8080&quot; &quot;HTTPS_PROXY=http://1.2.3.4:8080&quot; &quot;NO_PROXY=localhost,127.0.0.1,mycluster.icp,&lt;ICP ip address/range&gt;&quot;    </pre><blockquote>Note 1: There shouldn’t be any carriage return / new line within the [Service] stanza — Environment and HTTP_PROXY and NO_PROXY are on the same line and separated by a space.</blockquote><blockquote>Note 2: The NO_PROXY entry dictates that no proxy should be used for the IBM Cloud Private’s Docker private registry; make sure you add the docker-registry.mycluster.icp to whatever is the hostname of your private Docker registry and change &lt;ICPipaddress/range&gt; to the IP address range of your ICP nodes. For example 192.168.1.0/24. This is to make sure that Docker doesn’t use the proxy for inter-Docker communications.</blockquote><p><strong>2. Restart Docker</strong></p><pre>user@allnodes.icp:~$ sudo systemctl daemon-reload<br>user@allnodes.icp:~$ sudo systemctl restart docker</pre><p>More information on how to configure proxy settings for Docker is available <a href="https://docs.docker.com/config/daemon/systemd/#httphttps-proxy">here</a>.</p><p>Now, continue the IBM Cloud Private installation process normally until you’re about to manually edit the IBM Cloud Private config.yaml file.</p><p><strong>3. Customize the IBM Cloud Private </strong><strong>config.yaml file</strong></p><p>In the config.yaml file, there are tiller_http_proxy and tiller_https_proxy entries that needs to be added to configure an HTTP proxy throughout the installation:</p><pre>user@bootnode.icp:~$ sudo vi /opt/ibm-cloud-private-ee-2.1.0.3/cluster/config.yaml</pre><pre># Licensed Materials - Property of IBM<br># IBM Cloud private<br># @ Copyright IBM Corp. 2017 All Rights Reserved<br># US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.<br>---</pre><pre>## Network Settings<br>network_type: calico<br>## Network in IPv4 CIDR format<br>network_cidr: 10.1.0.0/16</pre><pre>## Kubernetes Settings<br>service_cluster_ip_range: 10.0.0.1/24</pre><pre>## Makes the Kubelet start if swap is enabled on the node. Remove<br>## this if your production env want to disble swap.<br>kubelet_extra_args: [&quot;--fail-swap-on=false&quot;]</pre><pre>...</pre><pre><strong>tiller_http_proxy: </strong><a href="http://1.2.3.4.8080"><strong>http://1.2.3.4.8080</strong></a><strong><br>tiller_https_proxy: http://1.2.3.4.8080</strong></pre><pre>...</pre><p>If you’re deploying Docker automatically using the IBM Cloud Private Installer, add the following Docker environment variables in your config.yaml file.</p><pre>## Docker Settings<br><strong>docker_env: [&quot;HTTP_PROXY=http://1.2.3.4:8080&quot;, &quot;HTTPS_PROXY=http://1.2.3.4:8080&quot;, &quot;NO_PROXY=localhost, 127.0.0.1, mycluster.icp, &lt;ICP ip address/range&gt;&quot;]</strong></pre><p>This will configure the Helm tiller daemon proxy settings in order to populate the IBM Cloud Private App Catalog.</p><p>Resume installation steps normally and that’s it.</p><p>After installation is complete, you can validate that the proxy entries have been correctly committed into IBM Cloud Private by accessing the /opt/ibm-cloud-private-ee-2.1.0.3/cluster/cfc-components/helm/helm-api.yaml file.</p><h4><strong>Password Protected Proxies</strong></h4><p>For password protected proxies make sure you use the following notation:</p><pre>http://username:password@1.2.3.4:8080</pre><h4>4. Post-Installation Proxy Configuration</h4><p>You can edit proxy settings post-installation, we just need to edit a few things:</p><ul><li>Go to <strong>Workloads -&gt; Deployments.</strong></li><li>In <strong>Deployments s</strong>earch for helm-api.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IiwWKZ1T7s8SbGAvHXNdDQ.png" /></figure><ul><li>Click on <strong>Edit</strong> and look for the following lines:</li></ul><pre>{<br>  &quot;name&quot;: &quot;HTTP_PROXY&quot;<br>},<br>{<br>  &quot;name&quot;: &quot;HTTPS_PROXY&quot;<br>},<br>{<br>  &quot;name&quot;: &quot;NO_PROXY&quot;,<br>  &quot;value&quot;: &quot;&lt;ICP cluster IP&gt;,mycluster.icp,cloudantdb,platform-identity-provider,localhost,127.0.0.1&quot;<br>},</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rAJ-JmOrUaa6bp3g45NR7Q.png" /></figure><ul><li>Edit the HTTP_PROXY and HTTPS_PROXY as you see fit.</li></ul><pre>{<br>  &quot;name&quot;: &quot;HTTP_PROXY&quot;,<br><strong>  &quot;value&quot;: &quot;http://1.2.3.4.8080&quot;<br></strong>},<br>{<br>  &quot;name&quot;: &quot;HTTPS_PROXY&quot;,<br>  <strong>&quot;value&quot;: &quot;http://1.2.3.4.8080&quot;</strong><br>},<br>{   <br>  &quot;name&quot;: &quot;NO_PROXY&quot;,<br>  &quot;value&quot;: &quot;&lt;ICP cluster IP&gt;,mycluster.icp,cloudantdb,platform-identity-provider,<strong>icp-management-ingress,platform-auth-service</strong>,localhost,127.0.0.1&quot;<br>},</pre><blockquote>Note: Depending on your environment, your NO_PROXY may vary; for example, mine included Kubernetes Ingresses and Services resources. It is important that NO_PROXY is correctly configured to avoid ICP nodes talking to each other over the proxy which will not work.</blockquote><ul><li>Click on <strong>Submit</strong> and you’re done.</li></ul><h3><strong>More information</strong></h3><ul><li><a href="https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.2/kc_welcome_containers.html">IBM Cloud Private documentation</a></li><li>IBM Cloud Private extensive config.yaml and Docker’s http-proxy.conf documentation in <a href="https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.2/installing/config_yaml.html#general_setting">Customizing the cluster with the config.yaml file</a></li><li>For assistance, ask questions on the public <a href="https://slack-invite-ibm-cloud-tech.mybluemix.net/">IBM Cloud Private Slack</a> channel or <a href="https://stackoverflow.com/questions/tagged/ibm-cloud-private">Stack Overflow</a>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=633d6e66021" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ibm-cloud/ibm-cloud-private-behind-a-proxy-633d6e66021">IBM Cloud Private Installation Behind a Proxy</a> was originally published in <a href="https://medium.com/ibm-cloud">IBM Cloud</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IBM Cloud Private Offline Installation]]></title>
            <link>https://medium.com/ibm-cloud/ibm-cloud-private-offline-installation-eb730ae13bfc?source=rss-ad66a1cb0000------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb730ae13bfc</guid>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[helm]]></category>
            <category><![CDATA[ibm-cloud-private]]></category>
            <dc:creator><![CDATA[Haytham Elkhoja]]></dc:creator>
            <pubDate>Wed, 02 May 2018 11:20:03 GMT</pubDate>
            <atom:updated>2018-05-18T14:15:51.710Z</atom:updated>
            <content:encoded><![CDATA[<p><em>By </em><a href="https://medium.com/u/940020e0c534"><em>Francis Nazareth</em></a><em>, Cloud Architect, IBM &amp; </em><a href="https://medium.com/u/ad66a1cb0000"><em>Haytham Elkhoja</em></a><em>, Cloud Platform Architect, IBM.</em></p><p>Enterprises around the world are revamping the way they build applications by adopting DevOps, Microservices, Cloud and Containers. But more often than not, enterprise customers working in highly regulated industries mandate a disconnected, private and air-gapped cloud — a cloud solution that is not connected to the internet.</p><p><a href="https://www.ibm.com/cloud/private">IBM Cloud Private</a> is a modular platform built on top of Kubernetes, Cloud Foundry and Terraform to help enterprises endorse a cloud-native approach to development and deployment of applications and rapidly bring app ideas to market. For more info on IBM Cloud Private (ICP) <a href="https://medium.com/ibm-cloud/ibm-cloud-private-in-plain-english-de0324051bba">check out this post</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*co2Wed_VA41CryMANB1Gtw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8H_oqXSEZP6NsCnETm3LVg.png" /></figure><h4>Goals</h4><p>This article has 2 goals:</p><ol><li>Demonstrate how to install and deploy IBM Cloud Private (ICP) in an offline enterprise environment (with no internet connectivity).</li><li>Populate the IBM Cloud Private App Catalog with offline Docker images to the private Docker registry and the private Helm chart repository.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2lN981HIdgjaReXy7_hpww.png" /></figure><p>The following sections go through installing IBM Cloud Private 2.1.0.2 on Red Hat Enterprise Linux 7.4 and publishing local Helm charts in the App Catalog.</p><p>There are 2 cases: <strong>Case 1: For IBM Cloud Private Cloud Native and Enterprise Editions</strong> and <strong>Case 2: For IBM Cloud Private Community Edition.</strong></p><h4>Assumptions and guidance</h4><p>This article assumes that:</p><ul><li>You have a common understanding of IBM Cloud Private. Please review the <a href="https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.2/getting_started/introduction.html">overview</a>, <a href="https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.2/getting_started/architecture.html">architecture</a> and <a href="https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.2/getting_started/components.html">components</a> sections of the IBM Cloud Private documentation in IBM Knowledge Center.</li><li>You have an internet connected laptop or host somewhere that you can use to git clone and do some docker pull.</li><li>You installed Red Hat Enterprise Linux 7.4 and have a valid ISO image or DVD medium at your disposal.</li><li>Enough disk space on /opt and /var. For more information on hardware and storage requirements, <a href="https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.2/supported_system_config/hardware_reqs.html">click here</a>.</li><li>You are a root. If not, all operations in this article should performed by a privileged user by prepending all commands with sudo.</li><li>Look out for the target of each command in the command line prompt. Some commands need to be applied on all nodes, others on the boot node and others on your internet connected laptop or host.</li></ul><h4>Installation</h4><p><strong>Download the Installer</strong></p><ul><li><strong>Case 1: For IBM Cloud Private Cloud Native and Enterprise Editions:</strong></li></ul><p>You must have a valid IBM Passport Advantage Subscription. Download the IBM Cloud Private 2.1.0.2 <a href="https://www.ibm.com/support/knowledgecenter/en/SSBS6K_2.1.0.2/installing/install_containers.html">Cloud Native</a> or <a href="https://www.ibm.com/support/knowledgecenter/en/SSBS6K_2.1.0.2/installing/install_app_mod.html">Enterprise</a> editions ibm-cloud-private-x86_64-2.1.0.2.tar.gz file and the supplied IBM Cloud Private Docker binary package icp-docker-17.09_x86_64.bin provided by IBM.</p><ul><li><strong>Case 2: For IBM Cloud Private Community Edition:</strong></li></ul><p>To install the <a href="https://www.ibm.com/support/knowledgecenter/en/SSBS6K_2.1.0.2/installing/install_containers_CE.html">IBM Cloud Private Community Edition</a>, the ICP installer is pulled via Dockerhub and saved on your laptop. Then, it is copied to the offline boot node. Run this command from your internet connected laptop:</p><p>user@macbookpro:~$ sudo docker pull ibmcom/icp-inception:2.1.0.2 &amp;&amp; sudo docker save -o icp-inception.tar ibmcom/icp-inception:2.1.0.2</p><p>Regardless of the medium that you want to use, whether it’s a Red Hat Enterprise Linux 7.4 DVD or an ISO image, you must mount it on your system.</p><p><strong>Mount the RHEL DVD drive or ISO Image</strong></p><p>Run the following command, substituting the name of your CDROM/DVDROM device (mine is /dev/sr0).</p><p>Repeat the following task on all the nodes.</p><p>DVD</p><pre>user@allnodes.icp:~$ sudo mount /dev/sr0 /media/cdrom</pre><p>ISO Image</p><pre>user@allnodes.icp:~$ sudo mount -t iso9660 -o loop path/to/image.iso /media/cdrom</pre><p><strong>Create a local Yum repository</strong></p><p>Repeat the following task on all the nodes.</p><pre>user@allnodes.icp:~$ sudo vi /etc/yum.repos.d/RHELDISC.repo</pre><pre>[RHELDISC]<br>name=RHEL_7.4_x86_64_Disc<br>baseurl=&quot;file:///media/cdrom&quot; -- or /media/iso<br>gpgcheck=0</pre><p>Run yum repolist to validate the list of repositories, including the local repo you’ve just created.</p><p><strong>Install other prerequisites</strong></p><p>Policycore utilities is a library needed by Docker. Install policycoreutils before installing Docker. This should use the local Yum repository previously created. Repeat the following task on all the nodes.</p><pre>user@allnodes.icp:~$ sudo yum install policycoreutils-python.x86_64</pre><p><strong>Prepare your cluster</strong></p><p>Follow the <a href="https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.2/installing/prep_cluster.html">steps here</a> to prepare your cluster and nodes. Repeat the following tasks on all the nodes. This will involve:</p><ul><li>Editing /etc/hosts.</li><li>Because IBM Cloud Private uses Ansible and SSH to install itself on all the nodes, from the boot node do an ssh user@&lt;node&gt; to all the nodes and to itself (localhost). This will add the nodes on the boot node’s ~/.ssh/known_hosts and clear the message The authenticity of host ‘xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx)’ can’t be established.</li><li>Installing python and python-pip.</li><li>Making sure NTP is deployed on all the nodes and time is sync’ed.</li><li>Tweaking some Kernel parameters in /etc/sysctl.conf.</li></ul><p><strong>Disable the Firewall</strong></p><p>Repeat the following tasks on all the nodes.</p><pre>user@allnodes.icp:~$ sudo systemctl stop firewalld<br>user@allnodes.icp:~$ sudo systemctl disable firewalld</pre><p><strong>Install Docker and load the IBM Cloud Private installation images to Docker</strong></p><ul><li><strong>Case 1: For IBM Cloud Private Cloud Native and Enterprise Editions:</strong></li></ul><p>Install Docker by running the following commands on all the nodes (not just the boot node). Please note that any dependencies will be resolved against the local yum repository.</p><pre>user@allnodes.icp:~$ sudo chmod +x icp-docker-17.09_x86_64.bin<br>user@allnodes.icp:~$ sudo ./icp-docker-17.09_x86_64.bin –install</pre><p>On your boot node, load the installer into Docker:</p><pre>user@bootnode.icp:~$ sudo tar xvf ibm-cloud-private-x86_64-2.1.0.2.tar.gz -O | docker load</pre><ul><li><strong>Case 2: For IBM Cloud Private Community Edition:</strong></li></ul><p>Follow <a href="https://docs.docker.com/install/linux/docker-ce/binaries/">this link</a> to download the Docker CE daemon and client binaries to your laptop. Copy the binaries with their prerequisites to all the nodes (not just the boot node), and continue the installation steps of Docker CE.</p><p>On your boot node, load the installer into Docker:</p><pre>user@bootnode.icp:~$ sudo docker load -i ~/icp-inception.tar</pre><p><strong>Create folders for the ICP installation and extract the sample configuration file from the installer image:</strong></p><pre>user@bootnode:~$ sudo mkdir /opt/ibm-cloud-private-2.1.0.2; \ cd /opt/ibm-cloud-private-2.1.0.2</pre><ul><li><strong>Case 1: For IBM Cloud Private Cloud Native and Enterprise Editions:</strong></li></ul><pre>user@bootnode.icp:~$ sudo docker run -v $(pwd):/data -e LICENSE=accept \ ibmcom/icp-inception:2.1.0.2-ee \ cp -r cluster /data</pre><ul><li><strong>Case 2: For IBM Cloud Private Community Edition:</strong></li></ul><pre>user@bootnode.icp:~$ sudo docker run -v $(pwd):/data -e LICENSE=accept \ ibmcom/icp-inception:2.1.0.2 \ cp -r cluster /data</pre><p><strong>Further prepare the installation</strong></p><p>Follow the steps <a href="https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.2/installing/install_containers.html">here</a> to further prepare the installation. This will involve:</p><ul><li>Generating SSH keys to allow for password-less SSH connections for Ansible. Follow the steps <a href="https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.2/installing/ssh_keys.html">here</a>.</li><li>Copying the SSH private key to /opt/ibm-cloud-private-2.1.0.2/cluster/ssh_key. Note that your copied private key is ssh_key and proper permissions should be applied.</li><li>Copying the installer to /opt/ibm-cloud-private-2.1.0.2/cluster/images/.</li><li>Customize and edit the IBM Cloud Private Installer files ./cluster/config.yaml and ./cluster/hosts.</li></ul><p><strong>Installing IBM Cloud Private</strong></p><p>You’re now ready to deploy IBM Cloud Private. From the boot node, run the following command:</p><pre>user@bootnode.icp:~$ sudo docker run --net=host -t -e LICENSE=accept \ -v &quot;$(pwd)&quot;:/installer/cluster ibmcom/icp-inception:2.1.0.2-ee install</pre><p>Alternatively, I prefer to perform my installation using screen to allow the installer to continue in case my terminal is killed or disconnected and verbosing as much as I can, then outputting the logs to an install.log file for debugging.</p><pre>user@bootnode.icp:~$ <strong>screen</strong> sudo docker run --net=host -t -e LICENSE=accept \ -v &quot;$(pwd)&quot;:/installer/cluster ibmcom/icp-inception:2.1.0.2-ee install <strong>-vvv | tee install.log</strong></pre><p>After the installation is complete, you should hopefully see this message:</p><pre>UI URL is https://&lt;ip_address&gt;:8443 , default username/password is xxx/xxx</pre><p><strong>Install the CLI tools</strong></p><p>There are 4 CLI tools that you need to use to continue your offline installation: kubectl, helm, the IBM Bluemix CLI bx and the bx icp plugin.</p><p><strong>Install the </strong><strong>kubectl command</strong></p><ul><li><strong>Case 1: For IBM Cloud Private Cloud Native and Enterprise Editions:</strong></li></ul><pre>user@bootnode.icp:~$ sudo docker run -e LICENSE=accept --net=host -v /usr/local/bin:/data ibmcom/icp-inception:2.1.0.2-ee cp /usr/local/bin/kubectl /data</pre><ul><li><strong>Case 2: For IBM Cloud Private Community Edition:</strong></li></ul><pre>user@bootnode.icp:~$ sudo docker run -e LICENSE=accept --net=host -v /usr/local/bin:/data ibmcom/icp-inception:2.1.0.2 cp /usr/local/bin/kubectl /data</pre><p>The preceding commands will copy the kubectl command into /usr/local/bin/kubectl. To test kubectl, open your installed IBM Cloud Private https://&lt;ip_address&gt;:8443, browse to the <strong>Configure client</strong> link on the top right side, and then copy and paste the kubectl config ... commands on the boot node command line prompt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3-wfMyj9jHaqorGWxENH0w.png" /></figure><p><strong>Install the </strong><strong>helm command</strong></p><ul><li>The IBM Cloud Private installation ships with helm. In the example below, you’ll be downloading the Linux (64-bit) version of the command.</li></ul><p>On your boot node, download it from the local /helm-api/cli URL.</p><pre>user@bootnode.icp:~$ curl --insecure -O <a href="https://mycluster.icp:8443/helm-api/cli/linux-amd64/helm">https://mycluster.icp:8443/helm-api/cli/linux-amd64/helm</a><br>user@bootnode.icp:~$ sudo mv helm /usr/local/bin/<br>user@bootnode.icp:~$ sudo chmod  +x /usr/local/bin/helm</pre><p>You also must download the helm command on your laptop or internet connected host: (assuming that your laptop can reach the master node to download the file, if not, then copy it via USB or another method). This will help us for later to package Helm charts for offline use.</p><p>If you’re on a macOS/Linux variant or on Windows with Chocolatey, you can download helm using the following commands:</p><pre><strong>macOS with brew</strong><br>user@macbookpro:~$ brew install kubernetes-helm</pre><pre><strong>Windows with Chocolatey<br></strong>C:\Users/user&gt; choco install kubernetes-helm</pre><p>Or simply follow the steps to download the Helm binaries <a href="https://docs.helm.sh/using_helm/#installing-helm">here</a>.</p><p><strong>Install the </strong><strong>bx command</strong></p><ul><li>From your laptop, download the Bluemix CLI from <a href="https://clis.ng.bluemix.net/download/bluemix-cli/latest/linux64">here</a>, then transfer the downloaded archive file to the offline machine.</li><li>From the boot node, unzip the tar.gz file and install.</li></ul><pre>user@bootnode.icp:~$ sudo tar -zxvf IBM_Cloud_CLI_0.6.6_amd64.tar.gz<br>user@bootnode.icp:~$ sudo ./install_bluemix_cli</pre><p><strong>Install the </strong><strong>bx cloud private plugin</strong></p><ul><li>On your newly installed IBM Cloud Private instance, browse to <strong>Command Line Tools &gt; Cloud Private CLI</strong>.</li><li>Download the plugin for your operating system/architecture. In our case, it’s Linux (64-bit). An icp-linux-amd64 binary file should start downloading. Transfer the downloaded binary file to the offline machine.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_T0hkqasKMyA81aM3rwthA.png" /></figure><ul><li>From the boot node, install the downloaded plugin using the bx command</li></ul><pre>user@bootnode.icp:~$ bx plugin install icp-linux-amd64</pre><ul><li>Now try logging in to your IBM Cloud Private instance using the bx command</li></ul><pre>user@bootnode.icp:~$ bx pr login --skip-ssl-validation -a https://&lt;ip_address&gt;:8443<br>username: xxx<br>password: xxx</pre><p><strong>Updating Helm Charts to use the local Docker registry</strong></p><p>Because your environment is not connected to the internet, the App Catalog will be empty. The App Catalog uses Helm chart repositories to populate Docker based applications that can be configured and deployed in seconds. By default, the App Catalog has 2 repositories, the publicly accessible Helm <a href="https://raw.githubusercontent.com/IBM/charts/master/repo/stable/">chart repo</a> located at <a href="https://github.com/IBM/charts">https://github.com/IBM/charts</a> and a local one, which is empty. Let’s populate it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f2B-dE7iAqlDJoDfLWkJuA.png" /></figure><p>Here are the steps that you will perform from your internet connected laptop or host:</p><ol><li>Pull the Docker images locally on your laptop, and create a local copy of necessary Docker images.</li><li>Tag these images (for example, a cluster named mycluster.icp and for the namespace default, an image named Jenkins needs to be tagged as mycluster.icp:8500/default/jenkins.</li><li>Push these Docker images to IBM Cloud Private’s private Docker registry.</li><li>Change the Helm charts to use Docker images from IBM Cloud Private’s private docker registry.</li><li>Update the Helm charts’ values.yaml files to the locations of the private Docker registry.</li></ol><p>This process can be tedious for a big number of images. To simplify the process, we have written a few shell scripts to automate all of this.</p><p><strong>Download ibm-helm-offline from github.com</strong></p><p>From your laptop, do the following:</p><pre>user@macbookpro:~$ git clone <a href="https://github.com/fnazaret/ibm-helm-offline.git">https://github.com/fnazaret/ibm-helm-offline.git</a><br>user@macbookpro:~$ cd ibm-helm-offline/<br>user@macbookpro:~/ibm-helm-offline$ chmod +x getRepos.sh</pre><p><strong>Edit DockerTags.txt</strong></p><p>Open the DockerTags.txt file. Edit the images, change the versions of the images if needed, or add more images from different Docker Hub repositories.</p><pre>user@macbookpro:~/ibm-helm-offline$ vi DockerTags.txt</pre><pre>ubuntu:14.04<br>ubuntu:16.04<br>websphere-liberty:latest<br>ibmcom/transformation-advisor-db:1.4.0<br>ibmcom/transformation-advisor-server:1.4.0<br>ibmcom/transformation-advisor-ui:1.4.0<br>ibmcom/postgresql:9.6.6<br>ibmcom/icp-nodejs-sample:latest<br>...</pre><p><strong>Execute the getRepos.sh file against the updated DockerTags.txt</strong></p><pre>user@macbookpro:~/ibm-helm-offline$ sudo ./getRepos.sh DockerTags.txt</pre><p>This script will use docker pull to pull the Docker images from Docker Hub, docker save, and then archive package them to a tar.gz file, ICP-EE-2.1.0.2.tar.gz. Depending on what you have included or excluded from the DockerTags.txt file, the size of the archive package might be slightly less than 9GB, hence the file creation will take time.</p><p>After completion, move the file ICP-EE-2.1.0.2.tar.gz and copy the contents of ~/ibm-helm-offline/ from your laptop to the bootnode host.</p><p><strong>Log in to the IBM Cloud Private private registry</strong></p><p>On your boot node do:</p><pre>user@bootnode.icp:~$ sudo docker login mycluster.icp:8500<br>username: xxx<br>password: xxx</pre><p><strong>Load the archive package into the IBM Cloud Private private registry</strong></p><pre>user@bootnode.icp:~$ tar xf ICP-EE-2.1.0.2.tar.gz -O | docker load</pre><p><strong>Execute the tagAndUpload.sh file against the DockerTags.txt</strong></p><pre>user@bootnode.icp:~$ chmod +x tagAndUpload.sh<br>user@bootnode.icp:~$ sudo ./tagAndUpload.sh DockerTags.txt</pre><p>Depending on the number of images and size, this might take some time to complete.</p><p>The images can now be deployed on IBM Cloud Private from the private registry, but the App Catalog is still empty. For that, you’ll need to perform 2 final tasks.</p><p><strong>Modify Helm chart entries from public to private registries</strong></p><p>The Helm charts need to be updated to point to the IBM Cloud Private private registry. For each Helm chart, you need to edit the registry entries in the values.yaml file, change the public registry entry to the private registry, create an archive of the Helm chart, and load the Helm chart to IBM Cloud Private.</p><p>For example, in ibm-datapower-dev/values.yaml, the line:</p><pre>repository: ibmcom/datapower</pre><p>should be changed to:</p><pre>repository: mycluster.icp:8500/default/ibmcom/datapower</pre><p>This has already been done for you in the in the ibm-helm-offline/stable folder on your laptop.</p><p>On your laptop, package the Helm charts needed. You need to execute helm package against that folder.</p><pre>user@macbookpro:~/ibm-helm-offline$ cd stable<br>user@macbookpro:~/ibm-helm-offline/stable$ helm package *</pre><p>This produces a .tgz file for each Helm chart. Copy them to the bootnode host.</p><p><strong>Load Helm charts to the private Helm charts repository</strong></p><p>You can now load the Helm charts that you packaged earlier into the IBM Cloud Private local Helm chart repository using this command from the boot node:</p><pre>user@bootnode.icp:~$ bx pr load-helm-chart --archive &lt;&lt;helm chart.tgz&gt;&gt;</pre><p>Alternatively, you could run the script loadHelmCharts.sh, provided in ibm-helm-offline:</p><pre>user@bootnode.icp:~$ chmod +x loadHelmCharts.sh<br>user@bootnode.icp:~$ sudo ./loadHelmCharts.sh</pre><p>The catalog should appear immediately in IBM Cloud Private App Catalog as soon as the command is run … and you’re done. Happy Kube’ing.</p><p>You can find more info on:</p><ul><li><a href="https://www.ibm.com/support/knowledgecenter/SSBS6K_2.1.0.2/kc_welcome_containers.html">IBM Knowledge Center page for IBM Cloud Private</a>.</li><li>On the Public <a href="https://slack-invite-ibm-cloud-tech.mybluemix.net/">IBM Cloud Private Slack</a> channel.</li><li>On <a href="https://stackoverflow.com/questions/tagged/ibm-cloud-private">Stackoverflow</a>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb730ae13bfc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ibm-cloud/ibm-cloud-private-offline-installation-eb730ae13bfc">IBM Cloud Private Offline Installation</a> was originally published in <a href="https://medium.com/ibm-cloud">IBM Cloud</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How IBM reinvented itself to become Cloud-native.]]></title>
            <link>https://medium.com/ibm-cloud/how-ibm-reinvented-itself-to-become-cloud-native-59c3455c9c98?source=rss-ad66a1cb0000------2</link>
            <guid isPermaLink="false">https://medium.com/p/59c3455c9c98</guid>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Haytham Elkhoja]]></dc:creator>
            <pubDate>Mon, 15 Jan 2018 19:33:36 GMT</pubDate>
            <atom:updated>2018-01-15T20:35:48.497Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FkMx9jk6N0rQO9tief6L9w.png" /></figure><p>The world is moving fast, new startups and technologies are disrupting, well… just about everyone. Companies big and small are reconsidering their strategies and architectures to gain a competitive edge. Whether it is providing a modern user feel and experience, offering mobile and social capabilities, or even harnessing AI and Cognitive solutions, transformation (digital or otherwise) is on everybody’s mind.</p><p>That’s why more and more discussions in IT revolve around Cloud-native and the subjects it drags along with it, mainly: Platforms, Analytics, Microservices, DevOps and SRE practices.</p><p><a href="https://www.ibm.com/blogs/bluemix/2017/09/microservices-and-cloud-native-development-vs-traditional-development/">As a recap</a>, Cloud-native applications are applications born on the cloud that take advantage of all of the facilities provided by the cloud such as elastic scaling, immutable deployments, as a service consumption and disposable instances. Cloud, whether public or private, is rapidly becoming the de-facto standard for deployment of new and modified applications.</p><h4><strong>So just how Cloud-native is IBM?</strong></h4><p>How can IBM help transforming your business into Cloud-native? How does IBM demonstrate the right commitment around Cloud-native and <strong>equip</strong> developers with the right tools of the trade to build the next generation of apps?</p><p>In <a href="https://medium.com/ibm-cloud/ibm-cloud-private-in-plain-english-de0324051bba">my previous post</a>, I briefly introduced <a href="https://www.ibm.com/cloud-computing/products/ibm-cloud-private/">IBM Cloud Private</a>, a platform that allows developers to design, build and then scale Cloud-native apps, behind the firewall, while consuming IBM’s Middleware, Analytics and other software as containerized Docker images.</p><p>Put simply, IBM Cloud Private is *the* Cloud-native platform of the future. It is built on top of Kubernetes+Cloud Foundry+Terraform and helps enterprises accelerate their Cloud-native journey by providing a pre-packaged enterprise-class solution, supported by IBM.</p><p>And because IBM Cloud Private comes bundled with Docker images and Helm charts for some of IBM’s most popular Middleware, it becomes evident to organizations running J2EE and Enterprise Applications (such as WebSphere, Db2, IIB and MQ) that IBM has already modernized its toolbox and portfolio of software while embracing substantial set of community-driven ingredients that help developers:</p><ul><li>Modernize and optimize existing applications</li><li>Open up enterprise data centers to work with cloud services, and</li><li>Create new cloud-native applications</li></ul><p>But here’s the grim truth. If your Cloud-native architecture doesn’t look as chaotic as the following depiction of Monolithic vs Cloud-native, then you’re doing it wrong.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*SD_Npzang0iqQQD9IyH0kw.png" /><figcaption>Source: <a href="https://www.thoughtworks.com/insights/blog/implications-tech-stack-complexity-executives">https://www.thoughtworks.com/insights/blog/implications-tech-stack-complexity-executives</a></figcaption></figure><p>The fact of the matter is that executing a successful Cloud-native journey doesn’t depend solely on the platform, but also on the architecture and practices developers adopt and utilize to achieve Cloud-native. And because Cloud-native apps follow the <a href="https://12factor.net/">12 Factor App</a> methodology, things like automation, portability, deployments and scalability need to be decided early on and catered by the application instead of the infrastructure. This sometimes means abandoning everything we know and opting for selecting on new methods, using new tools, and adopting a different point of view when it comes to infrastructure, security, networking, operation and management.</p><p>The implications are immense. Cloud-native development means that developers are hacking code, experimenting with different vendors, implementing new libraries, and scrutinizing unfamiliar frameworks. Due to the notion of “You build it, you run it” this also means that operational models are now handled by developers and developers want visibility and automation. Not only that, but the nature of microservices, which are at the root of Cloud-native applications, introduce new inherent challenges when integrating services in distributed systems.</p><p>All of this might seem overwhelming, challenging, or even confusing, and that’s why the point of this article is to guide you kickstart and feel confident about your Cloud-native undertaking.</p><h4>The IBM Cloud Native Landscape</h4><p>So allow me to introduce an unofficial IBM Cloud Native Landscape which is inspired by the <a href="https://github.com/cncf/landscape">Cloud Native Computing Foundation (CNCF) Landscape</a>.</p><p>This IBM Cloud Native Landscape is meant to provide enterprises, organizations, developers and sysadmins guidance on the tools we in IBM use (or support) in our Cloud-native products and projects.</p><p>A few examples:</p><ul><li>In a Cloud-native world, databases are meant to be consumed in a “as a Service” model and IBM has tons of enterprise-ready DBaaS such as <a href="https://www.ibm.com/cloud/cloudant">Cloudant</a>, <a href="https://www.compose.com/">Compose</a>, and <a href="https://www.ibm.com/cloud/db2-on-cloud">Db2-on-Cloud</a>, all managed and supported with solid SLAs.</li><li>For monitoring, traceability and logging IBM supports the likes of <a href="https://www.elastic.co/webinars/introduction-elk-stack">ELK</a>, <a href="https://zipkin.io/">Zipkin</a>, and <a href="https://prometheus.io/">Prometheus</a> stacks alongside <a href="https://www.ibm.com/cloud/hybrid-it-management/application-management">IBM Application Performance Management</a>.</li><li>For persistence and data consistency, IBM provides multiple Cloud-native Storage solutions such as <a href="https://www.ibm.com/cloud/object-storage">IBM Cloud Object Storage</a> and <a href="https://www.ibm.com/storage/spectrum">IBM Spectrum Scale</a>. IBM also supports <a href="https://www.gluster.org/">GlusterFS</a> deployments.</li><li>For service discovery, ingress, load balancing and service mesh, IBM supports NGINX and more recently, <a href="https://istio.io/">Itsio</a>, an effort led by <a href="http://www.eweek.com/cloud/google-ibm-lyft-collaborate-on-istio-open-microservices-technology">Google, IBM and Lyft</a> to provide management, security and traffic flow for microservices.</li></ul><p>The diagram below shows the different components that are either IBM branded, used within IBM products such as IBM Cloud Private, IBM Cloud Platform (Public), or supported and backed by IBM either through open source communities or foundations.</p><blockquote>Note: This diagram is not built or officially endorsed by IBM. The information provided below is accurate to the best of my knowledge. I will try to keep it up2date and current on a best-effort basis.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6TdbuPYnTw2RLGdDAWvCNg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_H53KzsmFJdBgps1S8cqeQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gwu2d8p4Y0FaziHOcU9IRA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3RofAFwtmakU9kgC0SfjQg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iXej-DXOWpQ2fwDhy0EGDg.png" /></figure><h4>Don’t do it alone</h4><p>The beauty about partnering with a company like IBM is that you’re not on your own.</p><p>First and foremost “Thinking” has to be the place to start, so I recommend taking the excellent <a href="https://www.ibm.com/design/thinking/">IBM Design Thinking Workshop</a> provided by the <a href="https://www.ibm.com/cloud/garage/">IBM Cloud Garage</a> team and available in multiple geos. The IBM Cloud Garages are intentionally designed to simulate creativity, learning, and transformation using the IBM Cloud Garage Method. Not only that, but IBM will assist partners and clients develop Cloud-native MVPs, contribute architectural guidance, prepare environments and transformation plans, and then finally offer managed services and SLAs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JSdgKQzZD_f-_kGDnKD_kA.png" /></figure><p>Second, nothing beats trying it in-house. As a proclaimed resident geek, I know I can’t learn something without trying it first. So if you’re starting your Cloud-native journey behind the firewall, you can try <a href="https://www.ibm.com/cloud-computing/products/ibm-cloud-private/">IBM Cloud Private</a> Community Edition at no charge. You’ll have many of the tools I discussed above and more.</p><p>On the other hand, if you want to innovate and consume on a public cloud and consume hundreds of public APIs and Cognitive/AI services on the <a href="https://www.ibm.com/cloud/">IBM Cloud</a>, you can try <a href="https://www.ibm.com/cloud/lite-account">IBM Cloud Lite</a> also at no charge.</p><p>Third, IBM has done a lot of prep-work for you. Our architects have done extensive re-engineering and Cloud-native journeys with many customers and have come up with patterns, reference architectures and sample code available to help you navigate and pilot your way in your journey.</p><p>Visit: <a href="https://github.com/IBM">https://github.com/IBM</a> and the <a href="https://www.ibm.com/cloud/garage/category/architectures/">IBM Architecture Center</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u18yjDb9u0o55tXvyiv-jg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59c3455c9c98" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ibm-cloud/how-ibm-reinvented-itself-to-become-cloud-native-59c3455c9c98">How IBM reinvented itself to become Cloud-native.</a> was originally published in <a href="https://medium.com/ibm-cloud">IBM Cloud</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IBM Cloud Private “… in plain English”]]></title>
            <link>https://medium.com/ibm-cloud/ibm-cloud-private-in-plain-english-de0324051bba?source=rss-ad66a1cb0000------2</link>
            <guid isPermaLink="false">https://medium.com/p/de0324051bba</guid>
            <category><![CDATA[cloud-foundry]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Haytham Elkhoja]]></dc:creator>
            <pubDate>Wed, 29 Nov 2017 17:41:48 GMT</pubDate>
            <atom:updated>2018-10-01T15:54:16.594Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/731/1*Ts27nWoaxqA7rvfrnhVa1Q.png" /></figure><p><a href="https://www.ibm.com/cloud/private">IBM Cloud Private</a> is here and the competition is heating up. After multiple workshops and client facing meetings, I realized that I wasn’t always sure how to articulate what IBM’s private cloud offering is in a few simple words. We sometimes get lost in the technical jargon and don’t always remember who the audience is, so here’s my attempt to explain ICP “in plain English”.</p><p>In a few words:</p><blockquote>IBM Cloud Private is a <strong>platform</strong><em> </em>to develop <strong>modern applications</strong><em> </em>based on <strong>micro-services architectures</strong><em> </em>behind the enterprise’s firewall while <strong>consuming</strong><em> </em>IBM’s catalog of <strong>middleware and software</strong><em> </em>.</blockquote><p>Now let’s take each buzzword and explain it:</p><ul><li><strong>Platform:</strong> A playground used by developers to develop, build, test, deploy and then scale applications.</li><li><strong>Modern Applications</strong>, or <strong>Cloud Native Apps:</strong> Applications that have been built natively on the cloud and have not been “lifted and shifted”. This means that they have been developed to make use of (and re-use) managed services provided by a Cloud platform such as Database as a Service (e.g. Cloudant and Compose), Elastic Caching (e.g. Redis) or API Security (e.g. API Connect). Remember that when building modern applications, developers “consume someone else’s service” more and “code from scratch” less.</li><li><strong>Microservices Architectures</strong>: Think of this as the next generation Service-Oriented Architecture (or SOA) that IBM pioneered. Instead of building one large monolithic application, developers split the application into small loosely-coupled applications (called services) that can be scaled, patched and updated independently. These apps know how to talk to each other to perform the actions needed.</li><li><strong>Middleware/Software:</strong> This means that developers will be able to consume and use IBM’s middleware and software as Docker images while building their modern micro-services application. Yes, ICP includes containerized/Docker images of many IBM software and middleware (MQ, Db2, WebSphere Liberty, DataPower, Integration Bus, Data Science Experience etc..).</li></ul><p>Most enterprises have been mandated to modernize their applications and infrastructures. They’re looking for new platforms, new frameworks, new architectures and new vendors to help them achieve Netflix-scale agility. In Middle East and Africa, this means banks, airline companies and telecom operators want to mimic the same experience their customers perceive when using born-on-the-cloud applications.</p><p>IBM Cloud Private gives enterprises the ability to:</p><ul><li><strong>Offer and Manage</strong> Container as a Service, Platform as a Service and Infrastructure as a Service.</li><li><strong>Refactor</strong> and modify current and legacy applications into cloud native apps. IBM Cloud Private can guide them through this process with capabilities such as the IBM Transformation Advisor and WebSphere Liberty.</li><li><strong>Innovate</strong> new born-on-the-cloud applications. ICP provides starter kits such as Microservices Builder and supports Open Source frameworks to jump-start their cloud-native journey.</li><li><strong>Protect</strong> investments. IBM Cloud Private provides the IBM Software and Middleware that clients rely on such as WAS, MQ, and Db2 etc. You can use IBM Cloud Private to run workloads on top of client’s new and refreshed Infrastructure as a Service including x86, POWER and Z… yes, Z as well.</li><li><strong>Safeguard</strong> and address security, risk and compliance. ICP provides the power of the cloud behind the firewall helping clients conform to strict regulations.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G-fUf_OgoXfOGDz7W_Wdlw.png" /></figure><p>IBM offers a great opportunity to help clients scale and host all their new modern apps, and “cloud-ify” current and legacy apps. IBM Cloud Private is IBM’s answer to the ever-growing demand for a private cloud and modern application platform that fits the enterprise in terms of compliance, security, support and services. Not only that. IBM Cloud Private is a step towards achieving <strong>Hybrid</strong> between IBM’s public and private clouds. Applications that run on <a href="https://www.ibm.com/cloud/private">IBM Cloud Private</a> will run on <a href="https://www.ibm.com/cloud/container-service">IBM Cloud Platform Container Service</a> or <a href="https://www.ibm.com/cloud/cloud-foundry">IBM Cloud Platform Cloud Foundry</a>.</p><p>Now for the geeks among us: IBM Cloud Private is a <strong>Kubernetes </strong>based platform that allows developers to push their <strong>Docker</strong> apps, push their code into <strong>Cloud Foundry</strong> or automate their cloud infrastructures using declarative <strong>Infrastructure as Code</strong>. IBM Cloud Private is built on and embraces open source.</p><p>Again, let’s take each buzzword and explain it:</p><ul><li><strong>Kubernetes</strong> or K8s: Inspired by Borg which is the container orchestration platform used at Google to scale thousands of containers. Kubernetes provides self-healing, scaling, load balancing, routing etc… Kubernetes aims to provide better ways of managing related, distributed components across varied infrastructure.</li><li><strong>Docker</strong>: A containerization technology that allows developers to package their code, frameworks and other dependencies into a single package that can be easily moved from one environment to the other. Docker does this by providing OS-level virtualization instead of Server-level virtualization. Docker solves code portability and environment uniformity while guaranteeing that the execution environment exposed to the application will be the same in development, testing, and production. This is also referred to as Environment Parity. Docker and Kubernetes are targeted mainly at DevOps.</li><li><strong>Cloud Foundry: </strong>A platform that offers an opinionated, prescribed and developer-friendly tools for developers to focus only on code and not have to worry about where the code will run. Cloud Foundry is targeted mainly at developers who aren’t too comfortable with Ops.</li><li><strong>Infrastructure as Code:</strong> The newest way of provisioning and managing Infrastructure (Load Balancers, Firewalls, Storage, Compute etc…). Instead of writing complex sequences of provisioning tasks to spawn environments or having to clone Terrabytes of OS images, templates and environments, Infrastructure admins can now write declarative charts that tell IBM Cloud Private “this is how I want my environment to look like, figure it out yourself.” IBM Cloud Private uses <strong>Terraform</strong> to make this happen and it works on IBM Cloud Platform, AWS, Azure and OpenStack as well. Terraform is targeted at Infrastructure, SysAdmins, DevOps and the adventurous Developers.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lwewv-AXc-KasCPOhvobjg.png" /></figure><p>You can try the <a href="https://www.ibm.com/account/reg/us-en/signup?formid=urx-20295">IBM Cloud Private Community Edition</a> at no charge!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de0324051bba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ibm-cloud/ibm-cloud-private-in-plain-english-de0324051bba">IBM Cloud Private “… in plain English”</a> was originally published in <a href="https://medium.com/ibm-cloud">IBM Cloud</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>