[Rebranding] HashiCorp

.github/workflows/ci-cd.yml

@@ -40,63 +40,7 @@ jobs:
         with:
           use-verbose-mode: "yes"
 
-  recipes-integration-tests:
-    name: Recipes Integration Tests
-    needs: [lint-unit, markdown-link-check]
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        os:
-          - ubuntu-1804
-          - ubuntu-2004
-          - ubuntu-2204
-        suite:
-          - docker
-          - docker-compose
-      fail-fast: false
-    steps:
-      - uses: actions/checkout@v2
-      - uses: actionshub/chef-install@main
-      - uses: actionshub/test-kitchen@main
-        env:
-          CHEF_LICENSE: accept-no-persist
-          KITCHEN_LOCAL_YAML: kitchen.dokken.yml
-        with:
-          suite: ${{ matrix.suite }}
-          os: ${{ matrix.os }}
-      - name: Print debug output on failure
-        if: failure()
-        run: |
-          set -x
-          sudo journalctl -l --since today
-          KITCHEN_LOCAL_YAML=kitchen.dokken.yml /usr/bin/kitchen exec ${{ matrix.suite }}-${{ matrix.os }} -c "journalctl -l"
-
-  docker-image-ci-cd:
-    name: Test & Release Docker Image
-    needs: [lint-unit, markdown-link-check, recipes-integration-tests]
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-      - name: Set up QEMU
-        uses: docker/setup-qemu-action@v2
-      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v2
-      - name: Test image Build
-        run: docker build -t jack20191124/aergia .
-      - name: Login to DockerHub
-        if: github.ref == 'refs/heads/master'
-        uses: docker/login-action@v2
-        with:
-          username: ${{ secrets.DOCKERHUB_USERNAME }}
-          password: ${{ secrets.DOCKERHUB_TOKEN }}
-      - name: Build and push
-        if: github.ref == 'refs/heads/master'
-        uses: docker/build-push-action@v3
-        with:
-          context: .
-          push: true
-          tags: ${{ secrets.DOCKERHUB_USERNAME }}/aergia:latest
+  aergia-ci-cd:
 
 
   documentation-ci-cd:

README.md

@@ -19,19 +19,52 @@ Aergia
 ![Last Commit]
 [![License Badge][License Badge]](https://www.apache.org/licenses/LICENSE-2.0)
 
-[Aergia][Aergia Documentation] is a tool that implements [Infrastructure-as-Code] through [CHEF cookbook]. It helps
-developers and organizations to rapidly prepare application **running environment** (on both bare-metal servers and 
-virtual machines) through various [CHEF recipes].
+Introduction
+------------
 
-As a strong supporter of [Infrastructure-as-Code], I choose [CHEF] to implement this concept, because my early career
-at Yahoo gave me great opportunities to see how CHEF was used as a critical CI/CD component at Yahoo's tech
-infrastructure. I learned that CHEF was a great tool and I would like to continue that journey with CHEF in my own
-projects.
+Aergia believes infrastructure is the "home" to software. The _highest-quality_ software are not possible unless backed 
+by the best-made tech infrastructure
 
-Note that although CHEF supports much more, Aergia automates **application environment setup ONLY** and does NOT
-automate any application deployment. For example, Aergia offers the ability to
-[install Docker Daemon](./recipes/docker.rb); but it does NOT support anything related to deploying a React app Docker
-container onto that server using Dockerfile.
+### Traditional Software Development
+
+![Error loading traditional.png](https://github.com/QubitPi/QubitPi/blob/master/img/hashicorp-aws/traditional.png?raw=true)
+
+I learned, from years of work experience, that thriving as a Software Engineer with their internal and external
+engagement demands requires high levels of _interpersonal sophistication_. It is no doubt then that the **single
+hardest task in teamwork is _efficient communication_**. This gets exacerbated in a software development cycle in which
+a developer has to distribute their communication efforts among **3** parties, which makes mis-communication frequent
+
+### How Big Techs Improve It
+
+![Error loading yahoo.png](https://github.com/QubitPi/QubitPi/blob/master/img/hashicorp-aws/yahoo.png?raw=true)
+
+By the time I joined Yahoo at 2016, the company had already made a
+[big move by removing all of its QA teams COMPLETELY][Yahoo removed QA]. Software developers were required to write
+automated tests by themselves using open source test frameworks, such as Groovy Spock, Jest, and Cypress. The software
+testing was then fully automated through [Yahoo's own CI platform][Screwdriver], which is developed on top of
+[Jenkins][Jenkins] originally.<br/><br/>This brought a big software quality improvements but in terms of communication
+quality, at least from my experience, was still not optimal. I've had such experience when I finshed implementing a
+system but waited for extra couple of weeks before DevOps Engineer set up a dedicated server for deployment. This
+virtually got mis-translated to my boss as "A software developer had his work delayed for couple weeks".
+
+### Software Development Tomorrow (What _HashiCorp AWS_ Does)
+
+![Error loading new.png](https://github.com/QubitPi/QubitPi/blob/master/img/hashicorp-aws/new.png?raw=true)
+
+The reason we still have DevOps staff is resource isolation using the ubiquitous Docker, which borns out of the
+traditional on-premise technology, is _manual_. With on-demand cloud, resource isolations are assumed NOT managed. We
+instead _manage business logics_ with efficiency ([Packer][Packer]) and immutability ([Terraform][Terraform]). **With
+HashiCorp + OpenStack Cloud, business no longer needs ~~Docker + k8s~~**. Teams and developers as well, with almost no
+overhead, are able to eliminate human DevOps<br/><br/>This is the picture from which I'm turning into reality in my
+team. Giving our developer fully **automated** control over infrastructure brings the following benefits to the team:
+
+- **Our developers learn more cutting-edge industry skills compared to their peers which makes our developers more
+  valuable along their career path**
+- **Taking hardware constraint into account causes a paradigm shift in how our engineers thought about problems, which
+  makes our developers better skilled and our software better in terms of quality**
+- **Eventually reduces the labor costs of company**
+
+[HashiCorp AWS][HashiCorp AWS] does exactly that.
 
 Documentation
 -------------
@@ -249,10 +282,9 @@ The use and distribution terms for [Aergia][Aergia] are covered by the
     </a>
 </div>
 
-[Aergia Documentation]: https://qubitpi.github.io/aergia/
+
 [Apache License, Version 2.0]: http://www.apache.org/licenses/LICENSE-2.0.html
 
-[CHEF]: https://qubitpi.github.io/chef-web-docs/
 
 [GitHub Workflow Status]: https://img.shields.io/github/actions/workflow/status/QubitPi/aergia/ci-cd.yml?branch=master&logo=github&style=for-the-badge
 
@@ -268,3 +300,15 @@ The use and distribution terms for [Aergia][Aergia] are covered by the
 [Why can't chef resolve my cookbooks?]: https://stackoverflow.com/a/26395418/14312712
 [Developing recipes with local mode]: https://subscription.packtpub.com/book/networking-and-servers/9781785287947/1/ch01lvl1sec21/developing-recipes-with-local-mode
 [Discord]: https://img.shields.io/discord/1060753787125514332?color=5865F2&logo=discord&logoColor=ffffff&style=for-the-badge
+
+
+
+
+[HashiCorp Terraform]: https://qubitpi.github.io/hashicorp-terraform/terraform/docs
+[HashiCorp Packer]: https://qubitpi.github.io/hashicorp-packer/packer/docs
+
+[Jenkins]: https://qubitpi.github.io/jenkins.io
+
+[Screwdriver]: https://screwdriver.cd/
+
+[Yahoo removed QA]: https://spectrum.ieee.org/yahoos-engineers-move-to-coding-without-a-net