Lab Zero: Create a Cloud Native Application in Less than 5 Minutes with zero Install

Transcription

1 Lab Zero: Create a Cloud Native Application in Less than 5 Minutes with zero Install Matthew Perrins, IBM Cloud Developer Services, mjperrin@us.ibm.com Benedict Fernandes, IBM Cloud Developer Services, bxf@us.ibm.com 1

2 Creating Cloud Native Applications with IBM Cloud App Service Create a Cloud Native Application in Less than 5 Minutes with zero Install 1. INTRODUCTION 3 2. CREATE AN IBM CLOUD ACCOUNT 6 3. CREATE AN IBM CLOUD CONTAINER SERVICE CLUSTER 9 4. CREATE A WEBAPP ON IBM CLOUD CONCLUSION EXTRA CREDIT: CONTINUOUS DELIVERY RESOURCES 26 ACKNOWLEDGEMENTS AND DISCLAIMERS 32 2

3 1. Introduction This lab walks you through the steps required to create, build and run a cloud native web application in less than 5 minutes with no installation. Along the way, you ll use the following services, and at each point, you ll see a client value statement to help you better position this with your clients: IBM Cloud App Service Offers a guided approach that enables you build cloud native apps in minutes. It eliminates the need to manually edit configuration files and allows you to easily add a select set of IBM Cloud Services to you project. Moreover, you can easily attach a DevOps Toolchain to your project that supports continuous integration and deployment to either a Cloud Foundry or IBM Cloud Container Service a managed Kubernetes-based environment on the IBM Cloud. While the Cloud App Service is free, it simplifies the construction and deployment of cloud native apps by easily integrating with other paid IBM Cloud Services. IBM Cloud Container Service It is a core part of the IBM One Cloud Architecture that combines container technology based on Docker with container orchestration based on Kubernetes. This service delivers powerful tools, and an intuitive user experience, with built-in security and isolation to enable rapid delivery of applications all while leveraging high-value IBM Cloud Services such as cognitive capabilities from Watson, Blockchain, IoT, and data-intensive applications among others. IBM Cloud Continuous Delivery Service enables teams to rapidly provision best-in-class DevOps tools from IBM, open source and others. Integration between these tools are configured automatically. IBM Cloud Continuous Delivery provides a core set of tools for any DevOps toolchain: Git repositories, issue tracking, delivery pipeline, and a Web IDE. The Delivery Pipeline orchestrates build, testing, and deployment jobs across multiple environments as changes progress from developer to production. These open and integrated set of tools enables automated delivery of cloud native applications with speed and control. 3

4 Creating Cloud Native Applications with IBM Cloud App Service For this lab, we are going to focus on an example cloud native web application architecture. We are going to build one part of this architecture: a simple Web Application. For more information on a Reference Implementation for building a cloud native OmniChannel Application using a Microservices architecture refer to IBM Garage Method: This lab requires the following: 1. An account with IBM Cloud. You may use your existing account or create a new account as shown in Section An IBM Cloud Container Service cluster 3. A web browser NOTE: Creating an IBM Cloud Container Service Cluster with the trial account can take some time, especially when multiple users are attempting to do this task in a shared environment. It is therefore recommended that you create this cluster ahead of the lab. Your track lead will provide this guidance. Additionally, you will be using the IBM Continuous Delivery Service to create a DevOps Toolchain. The IBM Continuous Delivery Service is currently only available in the US South region. Hence for this Lab to work correctly, please ensure that you are logged in to the US South Region. 4

5 At the conclusion of this lab, you will have completed the following steps: 1. Create a Java Spring Web Application 2. Configure this app for continuous delivery with a DevOps toolchain that includes: a GIT repository to store the source code for team based development, an Eclipse Orion webbased IDE, and a Continuous Delivery pipeline. This will deploy the app into the IBM Cloud Container Service runtime environment. 3. Deploy the Spring web app and access it via the web browser. You will end up with a simple Web Application ready for adding business logic: This Lab will walk through a web-based approach that uses the IBM Cloud App Service that provides a guided experience in constructing cloud native applications. The following diagram provides a graphical view of the steps described above. Although not explored in this Lab, there is also local tooling called the IBM Cloud Developer Tools (IDT) Command Line Interface (CLI) and IDE extensions that provide a more robust full developer life-cycle that includes creating new apps, local building and running with containers, and manual deployment of apps to the IBM Cloud. For more information in the IDT refer to: 5

6 Creating Cloud Native Applications with IBM Cloud App Service NOTE: If you do have an existing IBM Cloud account, skip Section 2(Create an IBM Cloud Account) and proceed to Section 3 (Create an IBM Cloud Container Service Cluster) If you do have an existing cluster on the IBM Cloud Container Service, skip Sections 2 and 3 and proceed to Section 4 (Create a Web App on IBM Cloud) 6

7 2. Create an IBM Cloud Account 1. To run these lab instructions, you will need to create a trial account on the IBM Cloud. You can do this free of charge and all the instructions contained in this lab do not incur any additional costs. 2. Create an IBM Cloud Trial account by navigating to this link. and click on Create a free Account. 3. Complete the Registration Form with your details and a valid address. 4. Click on Create Account. 5. Confirm your registration by accessing your and clicking on Confirm Account. 7

8 Creating Cloud Native Applications with IBM Cloud App Service 6. You can now log into IBM Cloud. 7. Click on Login and enter your and password 8. You will finally see the Dashboard View, which will be empty as you have not created any services or apps at this point. Please note the Region, Org and Space settings. Typically this will be US South, the Org setting will be same as your address and by default you are placed in a Space called dev, as shown below. 8

9 3. Create an IBM Cloud Container Service Cluster 1. If you are not already logged in to the IBM Cloud, log in by navigating to this link: 2. This Lab requires you to be in the US South Region. Please ensure your Region setting is as shown below. 3. From the IBM Cloud dashboard, click on the navigation menu: Then click on Containers to access the IBM Cloud Container Service, the cloud native app platform on IBM Cloud. 9

10 Creating Cloud Native Applications with IBM Cloud App Service 4. If you have an existing cluster it is recommended you delete it as shown below. 5. Later in this Lab, you will be using the IBM Cloud Continuous Delivery Service, which is currently only available in the US South Region. Hence it is necessary to ensure that the Region is set to US South as shown below. Click on the Create Cluster button to begin the creation of the Kubernetes cluster that will be managed by the IBM Cloud Container Service. 6. Verify that the cluster will be created in the US South region as shown below. Select the Free Plan type it is a great starting point for development and sandbox environments. It defaults to includes one Worker Node deployed to a secure shared environment, and does not offer production capabilities such as Load Balancing. See the IBM Cloud Docs for more information on the available plans. To proceed, enter a name in the Cluster Name field. This name needs to be unique, so use your name and a combination of date or something similar. Accept the defaults for the other fields. Click on Create Cluster. 10

11 You should see the cluster creation in progress as shown below. This is a Free tier cluster operating in a shared multi-tenant environment, hence this process may take several minutes (in the range of approximately 20 minutes). 11

12 Creating Cloud Native Applications with IBM Cloud App Service Select the Containers from the IBM Cloud menu as shown below While the cluster creation is in progress the State field will appear as Deploying. Upon successful cluster creation the State field will change to Ready. 12

13 Select the cluster and review the configuration of the Kubernetes cluster as shown below. Since this is a Free Tier Kubernetes cluster it can only be configured with a single worker note as shown below. 13

14 Creating Cloud Native Applications with IBM Cloud App Service 4. Create a Web App on IBM Cloud In this section, you will use the IBM Cloud to create a Spring web application using the IBM Cloud App Service from IBM. Access the IBM Cloud App Service Create from the Spring Basic Starter Kit Create a DevOps Toolchain for your app The IBM Cloud App Service jump-starts cloud native development by allowing a developer to create a project, pick an application starter kit and deploy a production-ready application within minutes to the IBM Cloud. The platform s code generation technology creates a starter application in the developer s preferred language and framework, which can be tailored to their needs and use case. Any services that are required in support of the use case, are provisioned automatically. Developers can debug and test on their local workstation or in the cloud, and then use the DevOps Toolchain to collaborate with others to automate the delivery process. 14

15 1. Start by logging in to IBM Cloud. While logged into the IBM Cloud, click on the Navigation menu in the header: Then click on Web Apps to access the IBM Cloud App Service cloud-native development experience on IBM Cloud. 2. Take a few moments to explore the main Overview screen for the IBM Cloud App Service. From here you may access and discover hand-picked content related to cloud-native development including the Resources, Community, and Starter Kits sections. As explained IBM Cloud provides two approaches to building cloud native apps a web-based and a CLI-based approach. This Lab will use the IBM Cloud App Service, which provides a web console. 15

16 Creating Cloud Native Applications with IBM Cloud App Service 3. Navigate to the Starter Kits menu on the left-hand side. You will see a range of starter kits that are designed to provide production code starting point for a variety of common cloud-native development use cases. They include patterns and technology framework stacks for key programming languages that are commonly used by developers. Have a look through the list of starter kits for other types of projects you may have in the future. 4. Scroll down the list and click on the tile labelled Java Spring Basic to select the Starter Kit. It is important to note that though this Lab uses the Spring Java framework as an example to build the application, other supported languages and frameworks include Java EE MicroProfile, Swift, Node.js and Python. 5. Within the Create New Project view, enter a sensible unique name, such as using your initials and a numerical counter (e.g. products-webapp-mjp01), this is important as the Web App will require a unique HTTP host name when it s running on the platform. Change the host to match the name of you app. Once you've completed the form, click on the Create Project button. 16

17 NOTE: Please ensure that you select US South as the Region. 6. The App Configuration/Details view is now displayed. This view is used to manage various aspects of an app: The right-hand side (1) offers a Getting Started Quickly guide. The main body has an area where you can create new and associate existing services to the app (2) The bottom of the screen offers an area where you may configure a DevOps toolchain (3) The bottom of the screen also offers an area where you may access credentials to any services that you have added to this app (4) 17

18 Creating Cloud Native Applications with IBM Cloud App Service At the top of the screen, it is possible to download the code (5) to the app without any DevOps configuration. Using the menu in the top right (6), you can also rename of the project or delete it. 7. We will now configure the DevOps environment for the app, and prepare for it continuous delivery. Click on the Deploy to Cloud button from your app's main view. 18

19 Developers can debug and test on their local workstation or in the cloud, and then use the IBM Cloud Continuous Delivery Service to collaborate with others to automate the delivery process. 8. You are given two choices for deployment: the popular Cloud Foundry framework, or the newer Kubernetes clusters that supports Docker and Helm deployments. For this lab we are using Kubernetes Clusters. 9. Select Kubernetes Cluster, select the cluster you had previously created, and click Create 10. You will see the Toolchain being created 19

20 Creating Cloud Native Applications with IBM Cloud App Service 11. After seconds you will see a green success message appear as shown below, indicating that the project is configured with IBM Continuous Delivery Service. Click on View Toolchain to view the associated toolchain that is now configured to manage this app. 12. A GitLab code Repository, an Eclipse Orion web based IDE, and a Delivery Pipeline is custom created for your app. Click on the Delivery Pipeline tile. 20

21 13. In the background, the DevOps Toolchain in the IBM Cloud is preparing a build of your initial release of the app and deploying it into the cloud. You should see the Build and Deploy stages have completed and the application is now deployed into the IBM Cloud Container Service. 14. Click on the Deploy Stage View Logs and History link to access the deployment log. Scroll to the last line of the deployment logs to find the link to access the container pod. 21

22 Creating Cloud Native Applications with IBM Cloud App Service 15. Open a new Browser window or tab and navigate to the link shown in the deployment logs. In this example, the link is: If for some reason any of these stages fail, re-run the stage as shown below. If the error persists, view the associated logs to identify the underlying error condition. 22

23 17. How long did the Build Stage take? 18. On the main Build Stage screen, as shown in the previous step, click on Build. The Duration below indicates how long the build took. 19. How long did the Deploy Stage take? 23

24 Creating Cloud Native Applications with IBM Cloud App Service 20. OPTIONAL: Back on the main Delivery Pipeline page, check the Deploy Stage configuration as shown below. Explore and identify the inputs and outputs of the Deploy Stage. Follow the same steps for the Build Stage. ***** Congratulations!!! You have successfully configured and built a Cloud Native Web Application with the IBM Cloud **** 24

25 5. Conclusion Congratulations! You have completed the lab. You have successfully used the IBM Cloud App Service to create a Web Application based on the Spring framework, configured it to deploy to a Kubernetes cluster on IBM Cloud and attached a custom DevOps Toolchain providing a continuous delivery pipeline for your app. This lab demonstrated how the IBM Cloud App Service enables developers to: Get started quickly with new cloud native projects, Enrich their applications by employing a rich catalog of services on the IBM Cloud, and Rapidly deliver their software by leveraging the powerful DevOps capabilities provided by the IBM Cloud. Next Steps: For future enhancements, you could try adding services such as a Database to enhance your app, or explore the other pattern starter-kits. Refer to Labs 1, 2, and 3 for other IBM Cloud development and deployment options available, including using the IBM Cloud Developer Tools CLI, VSCode plugins, and IBM Cloud Private. CONTACTS Matthew Perrins (mjperrin@us.ibm.com), STSM, Architect IBM Cloud Developer Services Benedict Fernandes (bxf@us.ibm.com), Offering Manager, IBM Cloud Developer Services 25

26 Creating Cloud Native Applications with IBM Cloud App Service 6. EXTRA CREDIT: Continuous Delivery View the Code Make Changes Invoke Delivery Pipeline to Deploy Updates 1. From the IBM Cloud menu, navigate to DevOps option to view the existing Toolchains configured. Select the relevant Toolchain. 2. From the Toolchains screen, Launch the Eclipse Orion Web IDE. 26

27 3. Eclipse Orion Web IDE now displays the project source code. Explore the various folders as shown below. 4. Open the index.html file in the src/main/resources/static/ folder. 27

28 Creating Cloud Native Applications with IBM Cloud App Service 5. Make an update to index.html and Save your changes by pressing <Ctrl+S> or by clicking File Save. 6. Now that the code is saved locally we need to do a Git commit and Git push to ensure the changes are reflected in the main Git repo. Launch Git as shown below. 7. Provide a brief description of the change and click Commit. 28

29 8. Push your changes to the primary Git repo by pressing Push. 9. Ensure there are no commit or push errors and observe the commit history as shown. 10. Navigate back to the Toolchain panel to invoke the Delivery Pipeline. 29

30 Creating Cloud Native Applications with IBM Cloud App Service 11. Initiate a build and deploy by clicking on the Delivery Pipeline tile. 12. Ensure Build and Deploy stages pass successfully. 30

31 13. Launch the new version of the application and check for the updates. 14. Congratulations: You made a change to your code, committed those changes to Git and used IBM Continuous Delivery Service to rapidly rollout those enhancements to your application. 31

32 Creating Cloud Native Applications with IBM Cloud App Service 7. Resources IBM Cloud App Service: Build a Node.js app to deploy on Containers to IBM Cloud - IBM Cloud App Service: IBM Cloud Container Service: IBM Cloud Garage Method: IBM Cloud Continuous Delivery Service: IBM Cloud DevOps: IBM Cloud Developer Tools: IBM DevOps Overview: Develop a Kubernetes App Toolchain: IBM Cloud App Service: IBM Cloud Developer Tools (IDT): Using the IDT: Jump Start Your Microservice Development: Spring@IBM Developer Center: Node@IBM Developer Center: 32

33 Acknowledgements and Disclaimers (v8) Copyright 2017 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission from IBM. U.S. Government Users Restricted Rights use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM. Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. This document is distributed as is without any warranty, either express or implied. In no event shall IBM be liable for any damage arising from the use of this information, including but not limited to, loss of data, business interruption, loss of profit or loss of opportunity. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided. IBM products are manufactured from new parts or new and used parts. In some cases, a product may not be new and may have been previously installed. Regardless, our warranty terms apply. Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice. Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary. References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation. It is the customer s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer s business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to interoperate with IBM s products. IBM expressly disclaims all warranties, expressed or implied, including but not limited to, the implied warranties of merchantability and fitness for a particular, purpose. The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual property right. IBM, the IBM logo, ibm.com, Aspera, Bluemix, Blueworks Live, CICS, Clearcase, Cognos, DOORS, Emptoris, Enterprise Document Management System, FASP, FileNet, Global Business Services, Global Technology Services, IBM ExperienceOne, IBM SmartCloud, IBM Social Business, Information on Demand, ILOG, Maximo, MQIntegrator, MQSeries, Netcool, OMEGAMON, OpenPower, PureAnalytics, PureApplication, purecluster, PureCoverage, PureData, PureExperience, PureFlex, purequery, purescale, PureSystems, QRadar, Rational, Rhapsody, Smarter Commerce, SoDA, SPSS, Sterling Commerce, StoredIQ, Tealeaf, Tivoli Trusteer, Unica, urban{code}, Watson, WebSphere, Worklight, X-Force and System z Z/OS, are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at: 33