cloud

Github with DI VonBriesen

Posted on

To get started, we got Github Accounts, and pulled open Github in Chrome. We downloaded github desktop and visual studio code. I ran into some problems with passwords and codes.

As we got ourselves started, we talked about how important building basic web pages and full stack development can be. The end goal here is to be able to show this to your students. asa job interview, if you cannot talk about version control, you’ll be booted from the interview. Github is a standard of version control methodology. Github version control can keep things clean and easy.

First its a file management tool. Next its a synchronization location between computers. Last it can be used for version control. Most websites require 5 pages, folder for scripts, folder for images, folder for styles. Git is the language or protocol for working with files.

We talked about protocols. We talked about the inventor of LINUX. We talked about how GIT hub was used to host files in the cloud for easy storage and retrieval. why would a small business want to have a server in their office? Github was bought for 7Billion by microsoft. there are over 100,000 abandoned software packages up there. There are also millions or billions of files there in active use.

We talked about dry code (well done work coded once) and wet code (repeated materials on multiple pages). Not everyone can do this in early classes, but as time moves on, it become essential. Everythin in Github is public. so cheating could occur. There is also an option for private to 3 individuals for free. So, some items can be private to the teacher and then hidden from classmates.

Repo is a repository. The extensions in here are MD. This represents Markdown language. The README.MD file will post its information by default at the bottom.

We had a chance to look at the repositories for this event.

  • Github based on Git
  • Linus Torvaldis created git after frustrations with existing (or non-existing) version control: https://en.wikipedia.org/wiki/GitHub
  • Took two weeks and applied his unique mindset… so some stuff is a bit… odd
  • Many use via CLI (Command Line Interface)
  • Github (not to be confused with git) was a company built around providing repositories (“repos”) using the git protocol.
  • Microsoft paid $7 BILLION for github in 2018
  • git and github have quickly moved to a dominant position in the version control space, with git now supported in a variety of environments and with many supporting tools, in addition to the original CLI

SO WHAT?

  • if your students graduate without version control experience you are doing them a disservice
  • it makes all kinds of things a lot easier, including: — maintaining copies of projects in multiple locations — collaborating with students and between students — tracking and merging changes — creating public repos, including webpage support (and wikis and tasks and much more)

Then we moved over into the tasks section.

TASKS

  • Remember IGNORE and EXPLORE (IE)
  • Create github account on http://github.com
  • Login (and stay logged in to) your email
  • Create a repo – — I suggest either NCCIA2020-LastnameFirstMI – i.e. NCCIA2020 von Briesen DI or — Course name in format YEAR-COURSEID-LastName or just COURSEID (i.e. CSC143-general or WEB110 von Briesen) — Github will put dashed wherever you have spaces in the repo name – you can change the name on the fly, but note what github changes your name to. — Choose options for creating a readme.md file and enabling web content
  • Edit your readme file — check out MD (MarkDown) tutorials/cheatsheets: https://guides.github.com/pdfs/markdown-cheatsheet-online.pdf – you can also use html — write something about your repo.
  • open up Github Desktop for Windows — login to your account — clone your repo — open your repo in visual studio and/or file explorer — create an index.html file with something simple like

    Yo! It’s my repo webpage!!

    — save this file. — make a change to the readme.md file (i.e. “I edited this document on my computer, not on the web!!”). Save this file. — note how the changes show up in github desktop. Commit changes (saves to repo) and push origin (pushes up to server). You cannot commit more than one file without updating the note (single files don’t require a note/summary). — view your repo on it’s website: http:/yourid.github.io/yourreponame

Commits are ways of saving to your repository

CHoose to initialize with readme. You can use this for an attendance task. First, you open your project folder and look at the files. Then you check them in your EDITOR. Then push them to the internet and check them on the web.

We opened up the repo, and adjusted the Readme. After saving, we can see the adjustments- with color changes.

If we’re making 2+ file changes, they must be committed individually. If no problem, add text and you’ll be allowed to commit to the repository.

We then moved to the online material and changed … then we saw the differences between fetch and pull. Fetch gets the original, pull open the issue. When conflicts take place, both sides are shown and you can work this out.

I see this is an easy way to keep materials together.

settings

Github pages

twdockery.github.io

Opening Keynote: Enter The Mesh

Posted on Updated on

At 9:00am on 10/22/2018, I attended the Opening Keynote session: Enter The Mesh, presented by Burr Sutter of Red Hat, at the All Things Open Conference at the Raleigh Convention Center in Raleigh, NC

Opening Keynote: Enter The Mesh

As before, Burr remains one of the fastest-talking-Hawaiian-Alabamian I’ve seen.  While I”m not terribly familiar with this software, I deeply appreciated his approach. Using his background to discuss his journey through open source as one similar to a martial arts movie, Burr moved us through a series of skill challenges, areas of growth and training, and mastery techniques required to excel. Using a close understanding of self-discovery, challenges followed by growth and training, he slowly built from an allegory of a talented and motivated individual growing into a seasoned professional into a short training sequeway. From the segueway, he rolled into specifics with Qpid dispatch, Amazon Web Services, and github.com

Service Mesh is also translated as a “service grid” as an infrastructure layer for inter-service communication. Buyanant CEO Willian Morgan explains what Service Mesh is in his article WHAT’S A Service Mesh? AND WHY DO I NEED ONE? Why cloud native applications require Service Mesh.

Below is an explanation of Willian Morgan ‘s Service Mesh.

It’s responsible for the reliable delivery of requests through the complex topology of services that comprise a modern, cloud native application. In practice, the Service Mesh is typically implemented as An array of lightweight network proxies that are deployed alongside application code, without the application needing to be aware.

Service Mesh Features

Service Mesh has the following characteristics:

  • Intermediate layer of inter-application communication
  • Lightweight network proxy
  • Application non-aware
  • Decoupling application retry/timeout, monitoring, tracing, and service discovery

Currently, two popular Service Mesh open source softwares, Istio and Linkerd , can be integrated directly into kubernetes, of which Linkerd has become a member of CNCF.

Understanding Service Mesh

If you use a sentence to explain what Service Mesh is, you can compare it to TCP/IP between applications or microservices, responsible for network calls, current limiting, fuses, and monitoring between services. For writing applications, there is usually no need to care about the TCP/IP layer (such as RESTful applications over the HTTP protocol), and the same use of Service Mesh does not require things between services that were originally implemented through applications or other frameworks. For example, Spring Cloud, OSS, just give it to Service Mesh.

Phil Calçado explains in detail the ins and outs of Service Mesh in his blog, Pattern: Service Mesh :

  1. Connect directly from the most primitive hosts using a network cable
  2. The emergence of the network layer
  3. Control flow integrated into the application
  4. Decompose the control flow outside the application
  5. Integrated service discovery and circuit breakers in the application
  6. There are packages/libraries dedicated to service discovery and circuit breakers, such as Twitter’s Finagle and Facebook’s Proxygen , which are still integrated inside the application.
  7. Open source software for service discovery and circuit breakers such as Netflix OSS , Airbnb’s synapse and nerve
  8. Finally appeared as the middle layer Service Mesh of the microservice

The architecture of Service Mesh is shown below:

Service Mesh runs as a sidecar, transparent to the application, and traffic between all applications passes through it, so control of application traffic can be implemented in the service mesh.

How does Service Mesh work?

Let’s take Linkerd as an example to explain how Service Mesh works. Another implementation principle of Istio as Service Mesh is basically similar to that of linkerd. Subsequent articles will explain how Istio and Linkerd work in kubernetes.

  1. Linkerd routes the service request to the destination address, and determines whether it is a service in the production environment, the test environment, or the staging environment according to the parameters in it (the service may be deployed in these three environments at the same time), is it routed to the local environment or the public cloud environment? All of these routing information can be dynamically configured, either globally or individually.
  2. When Linkerd confirms the destination address, it sends traffic to the corresponding service discovery endpoint, which is the service in kubernetes, and then the service forwards the service to the backend instance.
  3. Linkerd selects the fastest-responsive instance of all instances of the application based on the delay in which it observed the most recent request.
  4. Linkerd sends the request to the instance, recording both the response type and the delayed data.
  5. If the instance hangs, does not respond, or the process does not work, Linkerd will send the request to another instance and try again.
  6. If the instance continues to return error, Linkerd will remove the instance from the load balancing pool and periodically retry later.
  7. If the requested deadline has passed, Linkerd actively fails the request instead of trying to add the load again.
  8. Linkerd captures all aspects of the above behavior in the form of metric and distributed traces that are sent to the centralized metric system.

Why use Service Mesh?

Service Mesh didn’t bring us new features. It was used to solve problems that other tools have solved, but this time it was implemented in Cloud Native’s kubernetes environment.

In the traditional MVC three-tier web application architecture, the communication between services is not complicated, and it can be managed within the application itself. However, in the case of today’s complex large websites, the single application is decomposed into many micros. Services, service dependencies and communication are complex, with the “Fat Client” libraries like Finagle developed by Twitter , Hystrix by Netflix, and Stubby by Google. These are the early Service Mesh, but they are all suitable for specific The environment and the specific development language are not supported as platform-level Service Mesh.

Under the Cloud Native architecture, the use of containers gives more possibilities for heterogeneous applications, and the kubernetes enhanced applications have the ability to scale horizontally, allowing users to quickly compile applications with complex environments and complex dependencies, while developers Focus on program development without undue attention to the cumbersome things of application monitoring, scalability, service discovery, and distributed tracking, giving developers more creativity.

 

  

Additional Backup Slides To Keep Us Motivated

    

deck available  bit.ly/ato2018

 

Visual Communication Using Adobe Photoshop CC 2015 ACA Certification Achieved!

Posted on

Visual Communication Using Adobe Photoshop CC 2015 ACA Certification Achieved!

In the middle of the NCCIA conference, I had the opportunity to take a scheduled examination. The Adobe Certified Associate (ACA) certification allows you to demonstrate proficiency in Adobe digital communications tools. Become a Certified Associate and you will stand apart from your peers, boost your confidence, and expand your career opportunities.

The Visual Communication Using Adobe Photoshop exam validates skills in communication corresponding to Photoshop software. Adobe conducted research to identify the foundational skills needed to effectively communicate using digital media tools. Based on feedback from educators, design professionals, businesses, and educational institutions around the world, the objectives cover skill expectations for professional visual communication.

 

The following skills were assessed on the Visual Communication Using Adobe Photoshop exam:

  • Domain 1.0 Setting Project Requirements
    • 1.1 Identify the purpose, audience, and audience needs for preparing images.
    • 1.2 Demonstrate knowledge of standard copyright rules for images and image use.
    • 1.3 Demonstrate knowledge of project management tasks and responsibilities.
    • 1.4 Communicate with others (such as peers and clients) about design plans.
  • Domain 2.0 Identifying Design Elements When Preparing Images
    • 2.1 Demonstrate knowledge of image resolution, image size, and image file formats for web, video, and print.
    • 2.2 Demonstrate knowledge of design principles, elements, and image composition.
    • 2.3 Demonstrate knowledge of typography.
    • 2.4 Demonstrate knowledge of color correction using Photoshop.
    • 2.5 Demonstrate knowledge of image-generating devices, their resulting image types, and how to access resulting images in Photoshop.
    • 2.6 Understand key terminology when working with digital images.
  • Domain 3.0 Understanding Adobe Photoshop
    • 3.1 Identify elements of the Photoshop user interface and demonstrate knowledge of their functions.
    • 3.2 Demonstrate knowledge of layers and masks.
    • 3.3 Demonstrate knowledge of importing, exporting, organizing, and saving.
    • 3.4 Demonstrate knowledge of producing and reusing images.
    • 3.5 Demonstrate an understanding of and select the appropriate features and options required to implement a color management workflow.
  • Domain 4.0 Manipulating Images by Using Adobe Photoshop
    • 4.1 Demonstrate knowledge of working with selections.
    • 4.2 Use Photoshop guides and rulers.
    • 4.3 Transform images.
    • 4.4 Adjust or correct the tonal range, color, or distortions of an image.
    • 4.5 Demonstrate knowledge of retouching and blending images.
    • 4.6 Demonstrate knowledge of drawing and painting.
    • 4.7 Demonstrate knowledge of type.
    • 4.8 Demonstrate knowledge of filters.
  • Domain 5.0 Publishing Digital Images by Using Adobe Photoshop
    • 5.1 Demonstrate knowledge of preparing images for web, print, and video.

Cloud Computing Concepts Certification Acheived!

Posted on Updated on

Tyler Dockery achieves Cloud Computing Concepts Certification
Tyler Dockery achieves Cloud Computing Concepts Certification

Today, I completed my training by achieving a certification in Customer Resource Management (CRM) Concepts at Brainbench.com . This is one of several training subjects I am currently working on.