Skip to content

Latest commit

 

History

History
324 lines (171 loc) · 14.6 KB

CloudNative100.md

File metadata and controls

324 lines (171 loc) · 14.6 KB


Update: February 10, 2017

Introduction

This is the first of several labs that are part of the Oracle Public Cloud DevOps Cloud Native Microservices workshop. This workshop will walk you through the Software Development Lifecycle (SDLC) for a Cloud Native project that will create and use several Microservices.

You will take on 3 Personas during the workshop. The Project Manager Persona will create the projects, add tasks and features to be worked on, and assign tasks to developers.  The Project Manager will then start the initial sprint. The Java Developer persona will develop a new twitter feed service that will allow for retrieval and filtering of twitter data. The JavaScript Developer persona will develop a new Twitter Marketing UI that will display the twitter data to allow for analysis.  During the workshop, you will get exposure to Oracle Developer Cloud Service and Oracle Application Container Cloud Service.

Please direct comments to: Dennis Foley ([email protected])

Objectives

  • Create Initial Project
    • Add Users to Project
  • Create Product Issues
    • Create Issues for Twitter Feed Microservice
    • Create Issues for Twitter Feed Marketing UI
  • Create Agile Board and initial Sprint
  • Add Issues to Sprint

Required Artifacts

  • The following lab requires an Oracle Public Cloud account that will be supplied by your instructor.

Create Twitter Feed Marketing Project

Create Developer Cloud Service Project

STEP 1: Login to your Oracle Cloud Account

  • From any browser, go to the URL: https://cloud.oracle.com

  • click Sign In in the upper right hand corner of the browser

  • IMPORTANT - Under my services, select from the drop down list the correct data center and click on My Services. If you are unsure of the data center you should select, and this is an in-person training event, ask your instructor which Region to select from the drop down list. If you received your account through an Oracle Trial, your Trial confirmation email should provide a URL that will pre-select the region for you. (During XWeeks all accounts are in us2 data center)

  • Enter your identity domain and click Go.

    NOTE: The Identity Domain, User Name and Password values will be given to you by the instructor or Trial confirmation email. (Take DEVCS_DOMAIN value)

  • Once your Identity Domain is set, enter your User Name and Password and click Sign In

    NOTE: For this lab you will assume the role of Project Manager Lisa Jones. Although you are assuming the identify of Lisa Jones, you will log into the account using the username provided to you by your instructor, given to you by your corporation, or supplied to you as part of an Oracle Trial. As you progress through the workshop, you will remain logged in as a single user, but you will make “logical” changes from Lisa Jones the Project Manager to other personas.

  • You will be presented with a Dashboard displaying the various cloud services available to this account.

  • If all your services are not visible, click on the Customize Dashboard, you can add services to the dashboard by clicking Show. For this workshop, you will want to ensure that you are showing at least the Application Container, Developer and Storage cloud services. If you do not want to see a specific service, click Hide

STEP 2: Check/Set Storage Replication Policy

Depending on the state of your Cloud Account, you may need to set the replication policy, if it has not been previously set. In this step you will got to the Storage Cloud Service to check on the status of the Replicaton Policy.

  • Click on the Storage Cloud Service

  • If you see a message requesting that you Set Replication Policy as is shown below, click on the message. If the message is not displayed, your replicatin policy has already been set and you can continue to the next step by clicking on the Dashboard icon in the top right corner of the page.

  • Care must be taking when setting your replication policy, because it cannot be changed. With Trial accounts, the first option available will generatlly set the replication policy sufficient for this workshop, so we will take the Default, and click on the Set button.

  • Click on the Dashboard button

STEP 3: Login to Developer Cloud Service

Oracle Developer Cloud Service provides a complete development platform that streamlines team development processes and automates software delivery. The integrated platform includes an issue tracking system, agile development dashboards, code versioning and review platform, continuous integration and delivery automation, as well as team collaboration features such as wikis and live activity stream. With a rich web based dashboard and integration with popular development tools, Oracle Developer Cloud Service helps deliver better applications faster.

  • From the Cloud UI dashboard click on the Developer service. In our example, the Developer Cloud Service is named developer99019.

  • The Service Details page gives you a quick glance of the service status overview.

  • Click Open Service Console for the Oracle Developer Cloud Service. The Service Console will then list all projects for which you are currently a member.

STEP 4: Create Developer Cloud Service Project

  • Click New Project to start the project create wizard.

  • On Details screen enter the following data and click on Next.

    Name: Twitter Feed Marketing Project

    Description: Project to gather and analyze twitter data

    Note: A Private project will only be seen by you. A Shared project will be seen by all Developer Cloud users. In either case, users need to be added to a project in order to interact with the project.

  • Leave default template set to Empty Project and click Next

  • Select your Wiki Markup preference to MARKDOWN and click Finish.

  • The Project Creation will take about 1 minute.

  • You now have a new project, in which you can manage your software development.

Create Product Issues

Create Issues for Twitter Feed Microservice

STEP 5: Create Issue for the initial GIT Repository Creation

In this step you are still assuming the identity of the Project Manager, Lisa Jones.

  • Click Issues on left hand navigation panel to display the Track Issues page.

  • Click New Issue. Enter the following data in the New Issue page and click Create Issue.

    Note: Throughout the lab you will assign your own account as the “physical” owner of the issue, but for the sake of this workshop, Bala Gupta will be the “logical” owner of the following issues.

    Summary: Create Initial GIT Repository for Twitter Feed Service

    Description: Create Initial GIT Repository for Twitter Feed Service

    Type: Task

    Owner: Select your account provided in the dropdown [Logical Owner: Bala Gupta]

    Story Points: 1

    Note: Story point is an arbitrary measure used by Scrum teams. They are used to measure the effort required to implement a story. This Site will provide more information.

STEP 6: Create Issue for Update Twitter Credentials

  • Click New Issue. Enter the following data in the New Issue page and click Create Issue.

    Summary: Create Filter on Twitter Feed

    Description: Create Filter to allow user to supply text to reduce the amount of data returned by the Twitter feed

    Type: Feature

    Owner: Select your account provided in the dropdown [Logical Owner: Bala Gupta]

    Story Points: 2

STEP 7: Create Issue for initial GIT Repository creation

  • Click New Issue. Enter the following data in the New Issue page and click Create Issue. Note: The next two issues will logically be owned by John Dunbar.

    Summary: Create Initial GIT Repository for Twitter Feed Marketing UI

    Description: Create Initial GIT Repository for Twitter Feed Marketing UI

    Type: Task

    Owner: Select your account provided in the dropdown [Logical Owner: John Dunbar]

    Story Points: 1

STEP 8: Create Issue for Displaying Twitter Feed

  • Click New Issue. Enter the following data in the New Issue page and click Create Issue.

    Summary: Display Twitter Feed in Table Format

    Description: Display Twitter Feed in Table Format

    Type: Feature

    Owner: Select account provided in the dropdown [Logical Owner: John Dunbar]

    Story Points: 2

  • Click the back arrow on the left side of the window, or click on the Issues menu option to view all newly created issues.

Create Agile Board

Create Agile Board and Initial Sprint

Developer Cloud Service Agile Page Overview

Before you start using the Agile methodology in Oracle Developer Cloud Service, it is important that you know the following key components of the Agile page.

  • Board – A Board is used to display and update issues of the project. When you create a Board, you associate it with an Issue Query. The Board shows Issues returned by the Query. You can either use a Board created by a team member, or create your own Board. You can create as many Boards as you like.
  • Sprint – A Sprint is a short duration (usually, a week or two) during which your team members try to implement a product component. You add the product component related issues to a Sprint. When you start working on a product component, you start (or activate) the related Sprints. To update issues using a Sprint, you must first activate the Sprint and add the Sprint to the Active Sprints view.
  • Backlog view – Lists all Issues returned by the Board’s Query. The view also displays all active and inactive Sprints of the Board, and the sprints from other Boards that contain Issues matching the Board’s Query. Each Sprint lists issues that are added to it. The Backlog section (the last section of the Backlog page) lists all open issues that are not part of any Sprint yet. The Backlog view does not show the resolved and closed Issues.
  • Active Sprints view – Lists all active Sprints of the Board and enables you to update an Issue status simply by dragging and dropping it to the respective status columns.
  • Reports view – select the Burndown Chart tab to display the amount of work left to do in a Sprint or use the Sprint Report tab to list open and completed Issues of a Sprint.

STEP 9: Create Agile Board

  • Click Agile on the Left Side Menu to display a page listing all existing Boards

  • Click New Board and enter the following data. When done click Create.

    Name: Microservices

    Estimation: Story Points

STEP 10: Create Sprint

  • We will now create our first Sprint. Click New Sprint. Enter the following data and click OK.

    Name: Sprint 1 - Initial Development

    Story Points: 6

STEP 11: Add Backlog Issues to Sprint

  • Next, we want to add the backlog issues to the newly created spring. Drag and drop the 4 issues one at a time upward onto the Sprint 1 section. This will add the issues to the sprint.

Customize Agile Board

STEP 12: Customize Board

In the following step you will customize an Agile Board, and add a new Progress State. If you desire more information about States and Conditions, the following link will provide a tutorial: http://www.oracle.com/webfolder/technetwork/tutorials/obe/cloud/developer/AgileDevelopment/AgileDevelopment.html

  • Now we will show you how you can customize your board. In the right hand side click Board -> Configure

    Note: Before we create a new progress state, we want to un-assign some of the conditions that will be used in the new state. You can’t add new conditions or remove conditions, however, you can redefine progress states to suit your project’s needs and move conditions from one state to another. A large number of conditions are assigned to the Completed state by default.

  • Click on Progress States then click Completed state. In the lower left panel of the window, scroll down the conditions and select all the RESOLVED conditions. Click to move them over to Unassigned Conditions panel

  • Click New Progress State. Change Name to Verify Code. We will use this new State for performing QA and Testing.

  • Highlight all the RESOLVED unassigned conditions, and click to move them over to the Conditions column.

  • With Verify Code highlighted, click to move Verify Code above the Completed Process State.

  • Click Save to persist change.

STEP 13: Start Sprint

  • Click the Start Sprint button.

  • Leave the defaults and click Start

  • Now click on Active Sprints to view the Sprint Dashboard

  • Click on the Reports button to view the Burndown and Sprint reports.

  • You are now ready to move to the next lab.