Xeniais in the Enterprise Collaboration Industry

Xenia

xenia

230 Stories To Learn About Blockchain

178 Stories To Learn About Entrepreneurship

As we embrace the era of digital progress and transition to utilizing containers for our applications, we encounter a diverse range of core images that serve as the foundation for our apps. These images vary depending on our app's requirements, given the various methods we employ in building them. Unfortunately, in companies with a moderate level of DEVOPS experience (maturity levels 2 to 3), the emphasis often leans heavily towards expeditiously releasing new features, occasionally at the expense of security. For developers like us, the challenge lies in keeping pace with the ever-evolving realm of software. This encompasses the additional components they require (dependencies), the fundamental elements (components), and the tools (libraries) that facilitate their integration across our entire system. The amalgamation of all these elements is referred to as the Software Bill of Materials (SBOM). To address this, it is imperative to comprehend the SBOM of each image before utilizing it as a groundwork for our apps. However, manual execution of this process is intricate and time-consuming. Moreover, with every update to a newer image version, we must repeat the entire process, impeding our ability to deliver products promptly. The solution? Automation. By leveraging automation, we can navigate the intricate process of understanding the SBOM. It assists in creating organized lists of all components, identifying any known issues, and proposing solutions — all accomplished with tools such as Trivy. Before delving into the detailed steps, let's ensure that we are all aligned on the definition of SBOM. What is SBOM? SBOM stands for Software Bill of Materials, akin to a detailed inventory of all components constituting our software. This includes tools from external sources, building blocks, and even the regulations governing their usage, all with precise version details. SBOM holds significance as it provides a comprehensive view of all the disparate components converging to create a specific software. This aids our DevSecOps teams in identifying potential risks, understanding their implications, and taking proactive measures to address them, fortifying the security of our software. Why create SBOM? SBOM allows us to visualize all externally-sourced software, presenting different versions and highlighting potential security issues. Armed with this information, we can make informed decisions, particularly concerning libraries and tools from external origins. Finding and Managing Outside Parts: SBOM functions as a detailed map for our software, ensuring its safety and guarding against any subterfuge or attacks on our software supply chain. It serves as a tool to verify if our software sources adhere to robust security practices. Securing Our Supply Chain: SBOM Format An open standard serving as a software bill of materials, identifying and cataloging components, licenses, copyrights, security references, and other metadata related to software. While primarily enhancing license compliance, it also contributes to software supply-chain transparency and security improvement. Software Package Data Exchange (SPDX): Tags containing descriptive details about a specific software release, including product and version information. They also specify the organizations and individuals involved in producing and distributing the product, establishing a product's lifecycle. Software Identification Tags (SWID): The CycloneDX project establishes standards in XML, JSON, and protocol buffers. It offers an array of official and community-supported tools that either generate or work with this standard. While similar to SPDX, CycloneDX is a more lightweight alternative. CycloneDX (CDX): In addition to creating SBOM, Trivy has the capability to scan the SBOM generated either by Trivy or other tools to identify the severity of the problem. Alongside vulnerability detection, it suggests possible fixes for identified vulnerabilities. SBOM with TRIVY Trivy, a comprehensive security scanner maintained and built by the Aqua Security team, is reliable, fast, and equipped with several in-built scanners for detecting various security issues across different targets. It can be employed for scanning OS packages and software dependencies in use (SBOM), known vulnerabilities (CVEs), IaC misconfigurations, and sensitive information and secrets. Today, our focus will be on the SBOM scanning capabilities of Trivy. In this tutorial, we will: Create the SBOM using Trivy Analyze the created SBOM to scan and identify vulnerabilities For the demonstration, we will utilize one of the most widely used Docker images, NGINX, specifically , sourced from its Docker Hub image. We will run the scanner to generate the SBOM, and once generated, use it to obtain the list of vulnerabilities and potential fixes. nginx:1.21.5 Generating SBOM To generate the SBOM, ensure that Trivy is installed on your workbench. If not, you can install it using the commands provided in this . In my case, my PC is Debian-based, so I installed it using the following command: link sudo apt-get install wget apt-transport-https gnupg lsb-release
wget -qO - <https://aquasecurity.github.io/trivy-repo/deb/public.key> | gpg --dearmor | sudo tee /usr/share/keyrings/trivy.gpg > /dev/null
echo "deb [signed-by=/usr/share/keyrings/trivy.gpg] <https://aquasecurity.github.io/trivy-repo/deb> $(lsb_release -sc) main" | sudo tee -a /etc/apt/sources.list.d/trivy.list
sudo apt-get update
sudo apt-get install trivy If you are using any flavour of debian, you might face issue with “lsb_release -sc” in the command. To overcome the issue you can use one of the following values: wheezy, jessie, stretch, buster, trusty, xenial, bionic. Once installed you should see the following, when you run trivy --version Once the trivy is installed, we can scan the vulnerabilities in two ways, either for image, for the whole directory containing the files or an single file. For a folder containing group of language specific files trivy fs --format cyclonedx --output result.json /path/to/your_project For a specific file trivy fs --format cyclonedx --output result.json ./trivy-ci-test/Pipfile.lock For a container image trivy image --format spdx-json --output result.json nginx:1.21.5 Upon completion, the scanner will analyze the files or image to identify the programming language used in the application. Once identified, it will retrieve the database specific to that language, extracting the roster of libraries associated with it. The scanner then cross-references this list with the libraries utilized in the current context. The resulting compilation of these libraries, along with OS-level libraries, is presented in a Software Bill of Materials (SBOM), formatted according to our specified requirements. Listing Vulnerabilities of SBOM Once the SBOM are generated, we can create the list of known vulnerabilities of the dependencies in the image/files such as libraries, OS packages etc. In addition to identifying these, trivy also suggests the version in which these vulnerabilities are fixed, making it not an effective tool to identify the vulnerabilities but also to resolve them. In order for us to generate this list, we use the following command trivy sbom results.json This will generate the following list As you can observe, we get the name of the library, the CVE vulnerability Number, Its Severity (HIGH,MEDIUM,LOW), The status of Vulnerability fix( fixed, not fixed or will_not fix) , if its fixed then the fixed version and along with the details on the vulnerability. Based on this information ,we can upgrade the fixed vulnerable libraries, understand the vulnerability level in not fixed libraries and remove them if they are not required. In-addition to that, we would have the opportunity to look into the alternatives to the vulnerable libraries. For more information and documentation, visit this . site Liked my content ? Feel free to reach out to my for interesting content and productive discussions. LinkedIn

Identification of Vulnerable Images and Files Using SBOM With Trivy

204 Stories To Learn About Nft Art

116 Stories To Learn About Art

In this Kubeadm tutorial, we'll explore everything you need to know about Kubeadm commands and how to use them to create clusters & manage cluster components in (K8s). Kubernetes You'll not only learn how to create your own Kubernetes cluster using Kubeadm, but you’ll also master the art of managing cluster components, and discover Kubeadm's best practices. Join us on this exciting journey into the world of Kubeadm, where you'll unlock the power to with ease. orchestrate containers Let's dive in and become Kubeadm experts together! Before we dive deep into , what exactly is self-hosted Kubernetes (K8s)? kubeadm Content Overview What is Self-hosted Kubernetes? - Pros and Cons What is Kubeadm? Kubeadm Examples Top 20 Most Common Kubeadm Commands How to Create Kubernetes Cluster Using Kubeadm How to Manage Cluster Components with Kubeadm Kubeadm Best Practices What is Self-hosted Kubernetes? - Pros and Cons Self-hosted Kubernetes, also known as a "bare metal" or "on-premises" Kubernetes deployment, refers to running Kubernetes directly on physical or virtual machines without relying on a managed Kubernetes service provided by a cloud provider (such as EKS by AWS). Here are some pros and cons of self-hosted Kubernetes: Pros of Self-hosted Kubernetes 1. Full Control and Customization With self-hosted Kubernetes, you have complete control over the cluster configuration, networking, and infrastructure. This allows you to customize and optimize the cluster according to your specific requirements and infrastructure capabilities. 2. Cost Efficiency Self-hosting Kubernetes can be more cost-effective, especially for long-term deployments, compared to using managed Kubernetes services that often incur additional fees. Self-hosting allows you to leverage existing hardware resources and avoid the overhead costs of managed services. (and save a ton of money) 3. Security and Compliance Self-hosting Kubernetes gives you direct control over security measures, such as network policies, encryption, access controls, and compliance requirements. This allows you to implement the specific to your organization's needs and regulatory standards. (log4j, ring any bells?) best Kubernetes security practices 4. Resource Allocation Self-hosted Kubernetes allows you to allocate resources exclusively to your cluster without sharing them with other tenants. This enables better resource utilization and avoids potential performance issues that may arise from resource contention in a shared environment. Cons of Self-hosted Kubernetes 1. Infrastructure Management Self-hosting Kubernetes requires expertise in managing and maintaining the underlying infrastructure. You are responsible for provisioning, configuring, and monitoring the servers, networking, storage, and other components of the cluster. This can be time-consuming and require dedicated resources and additional hiring. 2. Scalability and Elasticity Scaling self-hosted Kubernetes clusters can be more complex compared to managed services that offer automated scaling capabilities. You need to plan and provision resources in advance to handle peak loads, and adding or removing nodes may require manual intervention. 3. Operational Complexity Self-hosted Kubernetes introduces additional operational complexities, such as managing upgrades, patches, backups, and high availability. These tasks require careful planning, testing, and coordination to ensure minimal disruption to the cluster and applications or else an increase in production downtime. What is Kubeadm? Kubeadm is a command-line tool that simplifies the process of setting up and managing a Kubernetes cluster, making it easier for technical community members to dive into the world of container orchestration. Think of as your trusty assistant who takes care of the nitty-gritty details of , allowing you to focus on the bigger picture. kubeadm cluster setup It automates complex tasks like configuring essential components, generating certificates, and ensuring your cluster follows best practices. Kubeadm Examples Let's take a look at some examples and commands to better understand how works. kubeadm 1. Initializing the Control Plane Example Command #1: ` ` kubeadm init Here's how to use the above command. kubeadm init --pod-network-cidr=192.168.0.0/16 This command initializes the control plane on the master node. It generates necessary certificates, sets up the API server, etcd, and other vital components. The ` ` flag specifies the IP address range for the pod network in the cluster. --pod-network-cidr 2. Joining Worker Nodes Example Command #2: ` ` kubeadm join kubeadm join <master-node-ip>:<master-node-port> --token <token> --discovery-token-ca-cert-hash <hash> This command joins a worker node to the cluster. You need to provide the IP and port of the master node, along with a token and discovery token CA certificate hash, which can be obtained during the control plane initialization. 3. Resetting a Cluster Command: ` ` kubeadm reset kubeadm reset --force This command resets a cluster, removing all the installed components and returning the node to its pre-Kubernetes state. The ` ` flag ensures a thorough reset. --force 4. Upgrading Kubernetes Version Command: ` ` kubeadm upgrade Here's how to use the above command. kubeadm kubeadm upgrade plan This command helps you upgrade your Kubernetes version. It checks for available upgrades and provides a plan for upgrading the control plane components. Top 20 Most Common Kubeadm Commands Here is a list of commonly used kubeadm commands, followed by a relevant example. 1. kubeadm init kubeadm init --pod-network-cidr=192.168.0.0/16 In the above example, the command initializes the control plane on the master node, generating certificates and setting up essential components. The ` ` flag specifies the pod network IP address range. --pod-network-cidr 2. kubeadm join kubeadm join <master-node-ip>:<master-node-port> --token <token> --discovery-token-ca-cert-hash <hash> The above command joins a worker node to the cluster by connecting to the specified master node using a token and discovery token CA certificate hash. 3. kubeadm reset kubeadm reset --force The above command resets a node, removing all installed Kubernetes components and returning it to its pre-Kubernetes state. The ` ` flag ensures a thorough reset. --force 4. kubeadm upgrade kubeadm upgrade plan The above command provides an upgrade plan, checking for available upgrades for the control plane components. 5. kubeadm token kubeadm token create This kubeadm command manages authentication tokens used for joining nodes to the cluster. This example generates a new token. 6. kubeadm config kubeadm config print init-defaults The above command manages kubeadm configuration files. This example prints the default configuration for cluster initialization. 7. kubeadm version kubeadm version The above command prints the version of kubeadm. 8. kubeadm config images kubeadm config images list Use the above command to print a list of images required for the current Kubernetes version. This command helps you determine the required for manual container image management. Replace ` ` with ` ` to pull config images. container images list pull 9. kubeadm token create kubeadm token create --print-join-command The above command generates a new token that can be used to join nodes to the cluster. The ` ` flag displays the join command to be executed on worker nodes. --print-join-command 10. kubeadm token list kubeadm token list The above command lists the active tokens along with their associated creation time and expiration. 11. kubeadm token delete kubeadm token delete <token_value> Use the above command to delete a specific token, rendering it unusable for node joins. 12. kubeadm config migrate kubeadm config migrate --old-config kubeadm.conf --new-config kubeadm.yaml The above command migrates a configuration file from an old version to a new version, enabling smooth upgrades of the configuration. 13. kubeadm certs kubeadm certs check-expirationkubeadm certs certificate-key The above commands check the expiration status of certificates used by the control plane components and provide warnings for certificates nearing expiration. The second command generates the key. 14. kubeadm init phase kubeadm init phase kubelet-start --config config.yaml From an InitConfiguration file, the above command creates a dynamic environment file with kubelet flags. 15. kubeadm join phase kubeadm join phase control-plane-prepare The above command executes a specific phase during the joining of a worker node to the control plane. This example runs the ` ` phase, which prepares the worker node to become a control plane node. control-plane-prepare 16. kubeadm kubeconfig kubeadm kubeconfig user --client-name=foo --config=bar Use the above command to output a file for an additional user named using a kubeadm config file bar. kubeconfig foo 17. kubeadm reset phase kubeadm reset phase preflight The above command executes a specific phase during the reset process of a node. This example runs the ` ` phase, which performs pre-reset checks before removing the Kubernetes components. preflight 18. kubeadm upgrade plan kubeadm upgrade plan The above command displays an upgrade plan for the control plane components, showing available versions and any required actions for the upgrade. 19. kubeadm upgrade apply kubeadm upgrade apply v1.22.2 Use the above command to apply a specific Kubernetes version to the control plane, upgrading its components to the specified version. 20. kubeadm upgrade node kubeadm upgrade node This command upgrades the and on a worker node to match the control plane's version. kubelet kube-proxy How to Create Kubernetes Cluster Using Kubeadm To create a Kubernetes cluster using , you need to ensure that your environment meets the necessary prerequisites. kubeadm Here's a step-by-step guide on how to create a Kubernetes cluster using , including the prerequisites, detailed instructions, examples, and commands. kubeadm Prerequisites Two or more machines running a supported Linux distribution (e.g., Ubuntu, CentOS, or Red Hat Enterprise Linux) with Docker installed. 2 GiB or more of RAM per machine is recommended; anything less leaves limited room for your software. Disable swap space on all machines. Set up a unique hostname, MAC address, and product_uuid for each machine. All machines in the cluster have complete network connectivity. You can connect to a public or private network. Open necessary ports (e.g., 6443, 2379-2380, 10250, 10251, 10252) in your firewall. Step 1: Install Docker and Kubernetes Tools On all machines, install using the for your Linux distribution. Docker Docker guide Install ` `, ` `, and ` ` using the following commands on all machines: kubeadm kubelet kubectl sudo apt-get update && sudo apt-get install -y apt-transport-https curlcurl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -echo "deb https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/kubernetes.listsudo apt-get updatesudo apt-get install -y kubelet kubeadm kubectlsudo apt-mark hold kubelet kubeadm kubectl Step 2: Initialize the Kubernetes Control Plane On the desired control plane node, initialize the cluster using the` ` command: kubeadm init sudo kubeadm init --pod-network-cidr=192.168.0.0/16 Note: Adjust the ` ` flag if you plan to use a different pod network. --pod-network-cidr After the initialization is complete, the command will output a ` ` command with a token and hash. Make sure to copy this command as it will be used to join worker nodes to the cluster later. kubeadm join Step 3: Set Up Cluster Configuration for kubectl On the control plane node, create the necessary directory and copy the file: kubeconfig mkdir -p $HOME/.kubesudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/configsudo chown $(id -u):$(id -g) $HOME/.kube/config Step 4: Deploy a Pod Network Addon On the control plane node, deploy a pod network add-on. For example, you can use Calico: kubectl apply -f https://docs.projectcalico.org/v3.21/manifests/calico.yaml Step 5: Join Worker Nodes in the Cluster On each worker node, run the ` ` command that was generated during the control plane initialization (from Step 2). This command typically looks like this: kubeadm join sudo kubeadm join <control_plane_IP>:6443 --token <token> --discovery-token-ca-cert-hash <hash> Step 6: Verify the Cluster On the control plane node, check the status of the cluster using ` `: kubectl kubectl get nodes Congratulations! You have successfully created a Kubernetes cluster using ` `. You can now deploy and manage your applications on the cluster. kubeadm How to Manage Cluster Components with kubeadm To manage cluster components with , you can use various commands to perform tasks such as upgrading the cluster, adding or removing nodes, and managing the control plane. kubeadm Here's a step-by-step guide on how to manage cluster components with , including detailed commands with code comments. kubeadm Step 1: Upgrading the Cluster Check the current version of Kubernetes on the control plane node: kubectl version --short Upgrade ` `, ` `, and ` ` on all nodes to match the desired Kubernetes version: kubeadm kubelet kubectl # Upgrade kubeadmsudo apt-get updatesudo apt-get install -y kubeadm=<desired_version># Upgrade kubelet and kubectlsudo apt-get updatesudo apt-get install -y kubelet=<desired_version> kubectl=<desired_version># Hold the packages to prevent automatic upgradessudo apt-mark hold kubeadm kubelet kubectl On the control plane node, initiate the upgrade process: sudo kubeadm upgrade plansudo kubeadm upgrade apply <desired_version> Upgrade the kubelet configuration on all nodes: sudo kubeadm upgrade node Verify the upgrade status: kubectl get nodeskubectl version --short Step 2: Adding Worker Nodes On the control plane node, generate a new command: kubeadm join sudo kubeadm token create --print-join-command On the worker node(s), run the command to join them to the cluster: kubeadm join sudo kubeadm join <control_plane_IP>:6443 --token <token> --discovery-token-ca-cert-hash <hash> Verify the status of the new worker nodes: kubectl get nodes Step 3: Removing Nodes Drain the node you want to remove: kubectl drain <node_name> --ignore-daemonsets On the control plane node, remove the node: sudo kubeadm reset On the control plane node, delete the node from the cluster: kubectl delete node <node_name> Step 4: Managing Control Plane Components Upgrade the control plane components on the control plane node: sudo apt-get update  sudo apt-get install -y kubeadm=<desired_version> kubelet=<desired_version> kubectl=<desired_version>  sudo kubeadm upgrade plan  sudo kubeadm upgrade apply <desired_version>  sudo systemctl restart kubelet Verify the upgrade status: kubectl get nodes  kubectl version --short Drain the control plane node you want to remove: kubectl drain <control_plane_node> --ignore-daemonsets On the control plane node, remove the control plane components using the following command. kubeadm sudo kubeadm reset On the control plane node, delete the control plane node from the cluster: kubectl delete node <control_plane_node> Note: Managing cluster components with requires caution, as it can impact the stability and availability of the cluster. Ensure you have a backup plan and follow the official Kubernetes documentation for detailed instructions specific to your setup and requirements. kubeadm Kubeadm Best Practices When used for its intended purposes, Kubeadm is an excellent tool. Here are three best practices to remember in order to use the proper tool for the job and get the most out of kubeadm. Use kubeadm only for production clusters that need autoscaling In general, kubeadm should not be utilized for production clusters because it lacks node and cluster autoscaling capability. This is due to the fact that node autoscaling necessitates controlling underlying infrastructure and hardware, which kubeadm delegated to other tools. Backup etcd on a regular basis Kubeadm does not have a multi-etcd cluster by default for storing cluster state. Make regular backups of etcd in case something goes wrong. Keep track of machines/nodes Kubeadm cannot power off machines that are not in use. So, in order to cluster using , you'll need to use an external solution to track worker nodes and their resource utilization. optimize cost in Kubernetes kubeadm Also published here. The lead image for this article was generated by via the prompt "containers" HackerNoon's AI Image Generator

Setting Up and Managing a Kubernetes Cluster with Kubeadm

Configuración y administración de un clúster de Kubernetes con Kubeadm

Configurer et gérer un cluster Kubernetes avec Kubeadm

Kubeadm के साथ Kubernetes क्लस्टर की स्थापना और प्रबंधन करना

Kubeadm を使用した Kubernetes クラスターのセットアップと管理

Configurando e gerenciando um cluster Kubernetes com o Kubeadm

Thiết lập và quản lý cụm Kubernetes với Kubeadm

使用 Kubeadm 设置和管理 Kubernetes 集群

Let's learn about via these 69 free stories. They are ordered by most time reading created on HackerNoon. Visit the to find the most read stories about any technology. Digital Art /Learn Repo 1. Is MangaDex Getting Shut Down After Being Targeted by The DMCA Subpoena? Sites offering manga comics, like MangaDex, allow users to access Manga without paying. This, of course, interferes with the business plans of Manga creators. 2. Actor Jordi Molla Plans Genesis NFT Drop with Krew Studios and Raini Krew Studios and Raini to launch Jordi Molla's inaugural NFT drop with a star-studded collaboration to accompany their highly anticipated new NFT release. 3. Is Value of NFT Fake or Real? An Economic Interpretation Does NFT actually represent something with genuine value? 4. Can NFTs Truly Impact The Art Market? (Part I) 5. Urpflanze JavaScript Library for Generative Art and Creative Coding Urpflanze is a javascript library to approach creative coding and generatve art 6. What Will Improv Comedy Look Like in the Metaverse? Two technologists work to bring Improv Comedy into the metaverse for the first time, raising the question of what the future of this artform will be. 7. This 2-Year-Old Artist Has Her Own NFTs Two-year-old Xenia Rose has already started working towards her dream of being a professional artist, with the launch of her first collection of NFTs. 8. Why NFTs Are The Future Of Online Art Trading? The art world is a highly lucrative industry, with a reputation for being both exclusive and enigmatic. 9. Metablaze to Introduce NFT based Perpetual Royalties on Ethereum Metablaze is introducing perpetual royalties to the Binance Smart Chain. 10. Exploring the Intersection Between Art & Technology In this piece, we’ll be discussing the various technological
revolutions that have directly impacted the world of art. 11. Nameless NFTs No More: The NCT Story NFTs shouldn't be nameless. Projects can use the original ERC20 utility token created for naming with ease. Explore why NCT is the ideal value added solution. 12. Blanket Statements Do Not Help Define NFTs Most people (bloggers and journalists included) don’t have the time or the dedication to dive deep into it or really think deeply about blockchain. 13. “I Don’t See NFT As a Bubble”, Sebastian Clej on NFT Art And Blockchain Technology Sebastian Clej on NFT Art And Blockchain Technology 14. Trials and Tribulations for AI Artist to Be Human Disappoints Human Girl AI artist, Al Gahaku, will “paint” more in a second than an artist's lifetime but the depth of human to human experience is lost until AI becomes human. 15. How To Create A Custom Digital Cartoon Character Drawing What can you do with your digitized art? 16. Colexion a Celebrity NFT Platform Raises $5 Million from Polygon, Titan Ventures and Maven Capital Colexion NFT Platform Raises $5 Million in Funding to expand operations in Asia. 17. Famous 3D Artist Gal Yosef Announces Meta Eagle Club Collection Backed by Fine Art Eden Gallery Famous 3D Artist Gal Yoseh Launches 3D NFT Collection as the NFT’s Become Mainstream. 18. NFTs Challenge The Art Industry's Dominance By The Wealthy Elites NFT's disrupt the legacy art world by giving power directly to artists and buyers. 19. Purr-fect New NFT Collection Who Keeps Waving Good Luck Back to its Collector Meow! The Lucky Maneki NFT is prowling around the blockchain spreading good luck and fortune to all who collect them! 20. NFT Boom 2.0: Is There Any Proof? The abbreviation NFT is becoming one of the most discussed topics in the world. Read about the impact this is having on the world. 21. How to Become an NFT Artist: a Step-by-step Breakdown of an NFT Plan Looking to become an NFT artist? Here is how you can become an NFT artist and fulfil your dreams to live a good life! 22. "NFTs Are The Perfect Bridge Between In-Game Items & Real-World Value" - Nick Rose of Ethernity In this article, Nick Rose discusses the future of NFTs and the collectables industry in the context of blockchain-based innovations. 23. How to Create Digital Generative Art With Python We create Generative Art with Python. No paintbrush required! In this tutorial, we're going to be using four pieces of code - painter, utils, numpy, and more. 24. Rediscovering the EverDragons, the First Cross-Chain NFTs With a group of friends and crypto archeologists, digging into the early history of Ethereum NFTs we discovered the EverDragons, minted in June 2018... 25. Software Development still seems a craft, but beautiful coding makes it an art. Although a lot of subjects in the field of software development reached a common understanding, one continues to be a matter of controversy: software development, is it craft or science? 26. Epix Industries' CBDO, says "in just a few days we gained 3,000 [NFT] collectors" Interview with Epix Industries. Epix Industries is building solutions, tools, and multiverses for the future of the professional NFT industry 27. Stickers NFTs Sold on Secondary Markets for as High as 50,000 USDT Stickers platform has become a very popular NFT platform when it comes to digital art. Stickers NFTs Sold on Secondary Markets for as High as 50,000 USDT. 28. Future of NFTs - why art is just the beginning Why NFT is a real revolution not only in the field of art but also in our digital identity. 29. Non-Fungible Tokens Are The Future How NFTs are the changing the game for owning a piece for true art. 30. Bitcoin NFTs are Getting Easier Every Day: Introducing Ordinals Bitcoin NFTs - technically called "Ordinals" are now available. This article will explain where to find them, how to buy them, and how to make them. 31. Right Click Save While it's true that you can just right-click-save an image rather than buy the NFT, this overlooks a couple of important things: provenance and the market. 32. What it Means to be a Creative Coder Programmers rarely agree on whether or not coding is a creative profession. My interest in coding always stemmed from what I could create with the code. Seeing an interesting visual result from my efforts is usually the most satisfying part. Most programmers are less concerned with how their app looks and more concerned with the functionality. Usually, as long as the app works the way it is supposed to, most programmers are satisfied. 33. Assessing the Impact of AI on Fine Art: Threat or Opportunity Last October was something of a watershed moment for contemporary generative art with the first sale by auction of a portrait generated with the help of artificial intelligence (AI) for $432,500, titled “Portrait of Edmond Belamy”. The event garnered a huge level of public interest, and received widespread media coverage across several major outlets, including the NY Times, the Washington Post and the Miami Herald, and from leading online Art news platforms Artsy and Artnet, among others. Aside from the final sale price greatly exceeding the original estimated sale price of $10,000, one of the most interesting aspects of this episode was how it was characterized by the media at large. 34. ‘My Nightmares Inspire My Art,’ Says NFT Artist kertburger I interviewed kertburger, a 2D and 3D digital artist on finding one's creative expression and how he got started with NFTs as a digital artist. 35. Some NFT Projects Have Weathered the Storm but the Majority Failed There have been poor outputs from much-hyped projects. Thankfully their day in the sun is over, making space for projects with tangible and intrinsic value. 36. Meet Tobias, the Creator of DALL·E's Game Tobias W. Kaiser, the creator of DALL·E's Game, speaks to HackerNoon about Web3, technology, and DAO. 37. Exploring NFT Galleries with Benjamin Agostini In this NFC interview, we spoke with Benjamin Agostini, Co-Founder of TheSafeBox.io. We discussed NFT art and galleries, and the future of NFTs and marketing. 38. Ayesha Mubarak Ali: A Pakistani Digital Artist Setting New Horizons with Her Unique Work Today’s rapidly evolving technological advancements and inventions have given a new meaning to the field of arts. 39. ATTENTION NFT Artists: Now is The Time to Buckle Down and Build The markets are down and crypto has been falling — so it’s the perfect time for artists to get to work on their next creation. 40. Soulbound Tokens — the Ultimate Proof of Belonging Proof of belonging is a commonly used concept in the crypto space and it more or less refers to a method of ascertaining that an individual is a legitimate..... 41. The Importance of Digital Assets and their Valuation Well, this article provides a comprehensive overview and analysis of digital assets and how to value them. 42. Non-Fungible Tokens Simplified: What Does NFT Really Mean? A simplified breakdown of non-fungible tokens (NFT), using easy-to-understand analogies and non-technical terms. 43. Building a Whole New World for the Fine Art Community ArtMeta is a metaverse designed to serve as a meeting place for artists and connoisseurs of fine art from all around the world. 44. Devised for Design: Top FIGMA Plugins Figma has been top of its game since its launch in 2016. Here's a list of our team's 12 most used plugins. 45. Putting the Art in Artificial Intelligence There are plenty of detractors who dislike the idea of AI-generated art, decrying it for its immediacy or availability to the masses. Others, see such tools as 46. Top 3 Most Expensive Meme NFTs Ever Sold The heroes of memes have recently returned from the past. And not for nothing, as you can see, the forgotten stars have already made thousands of dollars. 47. Blockchain + ART = Crypto-Art: An Analysis In 2019, the art market value was estimated to have crossed USD 64.1 billion, with close to USD 20 billion used on ancillary and external support services for the art market. 48. I Bought This Image For $1,500 (and I sold it for +50% in two weeks) Using NFTs NFTs are the newest hype. Millions of dollars in transactions and to tell you the truth, I love how they disrupted the art gallery space. 49. Whither NFTs? An Overview of The Progress of Non-Fungible Tokens in 2021 A stream of celebrities have released NFTs on marketplaces such as OpenSea, Rarible, and NBA Top Shot; capitalising on the boom of the incipient NFT market. 50. Non-fungible Sentiment: Exploring the Value of NFTs NFTs designed and run by real world crypto women are setting the bar high for digital art and the diverse use cases for identity-driven PFPs. 51. From Warhol to NFTs: The Evolution of Digital Art Digital art conjures up an image of something seemingly unrelated and totally extraneous to art: cryptocurrencies. 52. This Neural Network Paints Depressing Russian Cityscapes Russian doomer neural network creates paintings and music videos. Tutorial. Stylegan2 was trained on thousands of images of soviet architecture. 53. Conversation with an NFT Artist An interview with Pierre Bourque, NFT artist and founded of Blockchain Radio. 54. Blurring The Lines of Realism: Vancouver's First Outdoor Augmented Reality Art Gallery VMF connected artists with technical minds who transferred the artists' graphics into Spark AR. They curated Vancouver's first open-air AR Art Gallery. 55. Making a Music Visualization with P5JS I had the immense pleasure of attending several creative coding workshops on April 4th. They were streamed live on the SpacyCloud Twitch channel. There were additional sessions involving Hydra, Raspberry Pi, Haskell, and more. However for this post I want to focus on the first session which was a P5JS tutorial. In this post I hope to translate the P5JS tutorial into a written format, for posterity and to share what I learned. I'm going to review what was taught in the live session. Hopefully SpacyCloud will have another live stream in the future so I can catch up on what I missed. Here is the landing page for the event schedule. 56. Top 10 Potential Use Cases of NFT For Business NFTs could also be used as a form of currency. For example, businesses could issue NFTs that could be used to purchase goods and services from other businesses. 57. Predicting An Image Being Doodled, in Real Time - How We Built It. (Mind you, this is not a tutorial, I will be posting one soon though!) 58. Senshi: 5,555 Unique NFTs Inspired by 3D Art Senshi is the newest NFT project that is set to disrupt the industry. This project has 5,555 unique 3D NFTs and collectibles. Senshi is the latest project that 59. The eCommerce Turn of The Art Market: Trust, Transparency, And Trustworthiness Now that the online art marketplaces are finally going mainstream, how can the experience be matched to other online marketplaces? Data might be the key. 60. Generative Art: The Past, Present and Future Generative Art: The Past, Present and Future is a guide that explores the world of generative art, covering its history, techniques, tools, and future. 61. How Technology Enables Visual Artists to Create and Monetize Digital Art What are hottest NFT trends and what to expect in the field of digital art? 62. How NFTs and Museums are Creating A Digital Art Revolution NFTs (and their derivatives) are the future of art, and museums are the perfect place to start. Explore the latest trends in NFTs and how they're changing 63. Moving Beyond OpenSea A look into some of the issues with OpenSea, and some of the disruptors out there providing solutions 64. How To Protect Online Art Platforms From Cyber Attacks The potential cybersecurity threats that can thwart the long-awaited momentum of the online art market and how to avoid these risks. 65. What the Heck is a Numiz? As of 2021, there are three topics you don't discuss over polite conversation; politics, religion, and NFTs. But CryptoNumiz is here to change all that. 66. Facilitating Creativity with Expressive Programming Programming for art is easier than ever before with the help of high-level programming languages and programming libraries. Learn about some of the exciting Jav 67. Want to Buy NFTs!? Here Are 7 Reasons You Should! Why do I have to invest and buy some NFTs? Let's explore some objective reasons to get an NFT! 68. What You Don't Know About Non Fungible Tokens (NFTs) and Decentralized Finance (DeFi) With the rising popularity of cryptocurrency, the rise of a new generation of crypto-lovers has also fueled the growth of a new beast: non-fungible tokens. 69. How to Succeed in the NFT Art World as an Artist This article talks about NFT based digital art and how artists can succeed in the world of crypto art by selling their artwork to users. Thank you for checking out the 69 most read stories about Digital Art on HackerNoon. to find the most read stories about any technology. Visit the /Learn Repo

69 Stories To Learn About Digital Art

I’ve come to talk with you again Photo by on Shubham Dhage Unsplash I’ve written a whole bunch of blogs about running Cloud Foundry on Kubernetes. They all work, to varying degrees of success and have the support of a smattering of communities (read: companies with large budgets + engineers + open source ideals). Sometimes you just want BOSH. That sweet, sweet, familiar BOSH. Enter . bosh-lite What is ? bosh-lite works by spinning up a VM and placing BOSH on it. From there, you can use it to spin , , or anything else that has a BOSH manifest. bosh-lite cf-deployment zookeeper The BOSH director is configured with runtime configs, cloud configs, stemcells, releases, and all the other BOSH-like functionality you’ve come to expect. Installation The tool has been around forever, with a very good tutorial on installing and configuring located at . The rest of this blog assumes that you have followed these instructions up to step #7. bosh-lite https://bosh.io/docs/bosh-lite/ I had an issue with a newer version of VirtualBox (6.1.28), what worked for me is version 6.1.26 which is available . here It ends with an example deployment of which I guess is cool, but I’m guessing most BOSH directors are associated with a Cloud Foundry deployment. Read on for tips that maybe aren’t obvious from the documentation! zookeeper Deploying Cloud Foundry In -land there is documentation for using BBL to deploy and CF to . I point these instructions out in case you have an unlimited IAAS budget, however, I’ll show you how to deploy this to your Mac. cf-deployment bosh-lite GCP or AWS There is also a Readme within . I’ll be using this as the basis for the scripting below. cf-deployment For Operators Deploying CF to local bosh-lite Clone cf-deployment For these examples, I’ve assumed you will clone the CF repo to your home folder: cd ~

git clone https://github.com/cloudfoundry/cf-deployment.git Setup BOSH Environment variables This is spread across a few places in the documentation, I’ve gathered them all together: export CREDHUB_SERVER=https://192.168.56.6:8844
export CREDHUB_CLIENT=credhub-admin
export CREDHUB_SECRET=$(bosh interpolate ~/deployments/vbox/creds.yml --path=/credhub_admin_client_secret)
export CREDHUB_CA_CERT="$(bosh interpolate ~/deployments/vbox/creds.yml --path=/credhub_tls/ca )"$'\n'"$( bosh interpolate ~/deployments/vbox/creds.yml --path=/uaa_ssl/ca)"

export BOSH_CLIENT=admin
export BOSH_CLIENT_SECRET="$(bosh int ~/deployments/vbox/creds.yml --path /admin_password)"
export BOSH_CA_CERT="$(bosh interpolate ~/deployments/vbox/creds.yml --path /director_ssl/ca)"
export BOSH_ENVIRONMENT=vbox

bosh alias-env vbox -e 192.168.56.6 --ca-cert <(bosh int ~/deployments/vbox/creds.yml --path /director_ssl/ca) You might consider adding this to your bash/zsh profile. Upload Stemcell, Cloud Config and Runtime Config bosh upload-stemcell --sha1 f399044d2ebe3351f0f1b0b3f97ef11464d283b4 "https://bosh.io/d/stemcells/bosh-warden-boshlite-ubuntu-xenial-go_agent?v=621.125"
bosh update-runtime-config ~/workspace/bosh-deployment/runtime-configs/dns.yml --name dns
bosh update-cloud-config ~/cf-deployment/iaas-support/bosh-lite/cloud-config.yml As time goes by, CF may complain of wanting a newer stemcell version, update the command with the requested version. The version and are listed , note that uses stemcells. bosh upload-stemcell sha1 here bosh-lite warden Go Get a Drink This part will take around 45 minutes to complete, unless you’ve changed the IP address of the BOSH director, the following command will deploy CF. cd ~/cf-deployment
bosh -e 192.168.56.6 -d cf deploy \
  cf-deployment.yml \
  -o operations/bosh-lite.yml \
  -v system_domain=bosh-lite.com Log Into CF This is done in two steps, targeting the API and then logging in, pulling the admin password out of credhub without printing it to the screen: cf api https://api.bosh-lite.com --skip-ssl-validation
cf login -u admin -p $(credhub get -n $(credhub find -n admin | grep cf_admin | cut -d: -f2) | grep value | cut -d: -f2) -o system -s test Tada! Create a space and start pushing apps. (Optional) Setup SSH to BOSH Director Why? I like to be able to SSH to my BOSH Director to poke around. I’m weird. This is not required for the CF deployment, but nice to have: bosh int ~/deployments/vbox/creds.yml --path /jumpbox_ssh/private_key > ~/deployments/vbox/jumpbox.key
chmod 600 ~/deployments/vbox/jumpbox.key
ssh jumpbox@192.168.56.6 -i ~/deployments/vbox/jumpbox.key Beware of Dragons Issue #1 – Reboot Rebooting your Mac causes to misbehave, badly, unless you follow a couple of easy steps. bosh-lite Before shutdown: In Oracle VM VirtualBox Manager select the VM, right click and navigate to > Close Save State After reboot: In Oracle VM VirtualBox Manager select the VM, right click and navigate to > Start Headless Start Even performing these steps I can’t always bring the BOSH Director back online. If you have accidentally rebooted the host you can recreate the BOSH director using the state file and use to recover the broken CF deployment: bosh cck cd ~/deployments/vbox

bosh create-env ~/workspace/bosh-deployment/bosh.yml \
  --state ./state.json \
  -o ~/workspace/bosh-deployment/virtualbox/cpi.yml \
  -o ~/workspace/bosh-deployment/virtualbox/outbound-network.yml \
  -o ~/workspace/bosh-deployment/bosh-lite.yml \
  -o ~/workspace/bosh-deployment/bosh-lite-runc.yml \
  -o ~/workspace/bosh-deployment/uaa.yml \
  -o ~/workspace/bosh-deployment/credhub.yml \
  -o ~/workspace/bosh-deployment/jumpbox-user.yml \
  --vars-store ./creds.yml \
  -v director_name=bosh-lite \
  -v internal_ip=192.168.56.6 \
  -v internal_gw=192.168.56.1 \
  -v internal_cidr=192.168.50.0/24 \
  -v outbound_network_name=NatNetwork --recreate

bosh cck If that doesn’t work, you can completely wipe and recreate the BOSH and CF deployment by: Logging into Oracle VM VirtualBox Manager, select the VM, right click and select > Remove Delete all files Delete the state file at ~/deployments/vbox/state.json Rerun the command then redeploy CF. bosh create-env Issue 2 – Networking issues If you get: Deploying:
  Creating instance 'bosh/0':
    Waiting until instance is ready:
      Post "https://mbus:<redacted>@192.168.56.6:6868/agent": dial tcp 192.168.56.6:6868: connect: connection refused

Exit code 1 You probably skipped the step to add the host routing: sudo route add -net 10.244.0.0/16     192.168.56.6 Final Thought We all deserve nice things. is one of those nice things for folks who enjoy BOSH and want to use it on their own computer. bosh-lite Enjoy! Also published . here

Spin Up a BOSH VM Faster Using BoshLite

This article provides the network vulnerabilities and defense approaches, with a focus on all the TCP and UDP ports, Port vulnerability, and learn more about Windows, Linux server operation guide. ★ Every organizational network has security Weaknesses in its system and it will be explored by the intruders using tools and techniques. ★ After a discussion of the risks that are associated with TCP/UDP ports, we will present a defense of the network in this article everything from preventing access to the port to protecting the network after it has breached a port. To provide a stable networking environment and deter certain classes of security breaches on your cloud servers/campus network/Office network. Please. Follow the guide to implement a standard firewall system on your servers. ★ Vulnerability Protection provides advanced server security for your cloud/physical servers/PCs. It protects enterprise applications and data from breaches and business disruptions without requiring emergency patching on uncertainty. ★ These broad sets of measures will help you maintain the Linux server and helps you to simplify the overall security operations hustle-free. ★ In the computer world, we use a network port as a communication line between two endpoints. At the software level, within an operating system, a port is a logical construct point that singles out a specific process or a network service. We identify ports for each protocol and address combination by using 16-bit unsigned numbers, commonly known as the port number. The most popular protocols that we use in routine life are TCP and UDP. ★ We identify a network port number with an IP address of a host and the protocol used for the communication. This process is well-known as binding and enables the process to send and receive data via the network correctly to the origin and destination. It completes the destination or origination network address of a message. IANA reserved specific port numbers to identify specific services so that a reaching packet could be forwarded to a running service. Internet Assigned Numbers Authority (IANA) functions: (i) Domain Names Management of the DNS Root Zone (assignments of ccTLDs and gTLDs) along with other functions such as the .int and .arpa zones. Root Zone Management Database of Top Level Domains .int Registry .arpa Registry IDN Practices Repository (ii) Number Resources Coordination of the global IP and AS number spaces, such as allocations made to Regional Internet Registries. IP Addresses & AS Numbers Network abuse information (iii) Protocol Assignments The central repository for protocol name and number registries used in many Internet protocols. Protocol Registries Apply for an assignment Time Zone Database ★The IANA is responsible for the global coordination of Internet protocol resources, such as the DNS Root, IP addressing, and the registration of commonly used port numbers for well-known Internet services. It divides the port numbers into three areas: Well-Known Ports: 0 through 1023 Registered Ports: 1024 through 49151 Dynamic (Private Ports): 49152 through 65535 ★ Well-Known and Registered we should not use ports without IANA registration. To register for a port and services. Please, refer to this weblink for more information. ★ This are used to register user-specific port numbers and service names in the IANA council. To get to know more about the detailed instructions on how to fill out the applications of this form, please read the procedures document . Service Name and Transport Protocol Port Number Registry form (RFC 6335) — — — — — — MASTER CHART OF TCP/UDP PORTS — — — — ★I have designed a master chart of TCP/UDP ports with several categorizations to identify the ports effectively and efficiently. Well Know Port Numbers and its vulnerabilities The ports in this table are used with protocols that transfer files. File Transfer Ports: The ports in this table are used with email related protocols. Email Ports: The ports in this table are associated with protocols used to connect to remote computers for various purposes. Remote Access Ports: The ports in this table don’t fit neatly in any of the other categories but are still relevant. Miscellaneous Ports: Firewall Operation Guide Follow the guide to implement a standard firewall system on your servers. How to Close Unused Open Ports: TCP and UDP Ports : Open ports allow hackers to: ✓ Unused services tend to be left with default configurations, which are not always secure, or maybe using default passwords.which leads to an attack. Close unused service: ✓ : Unused services tend to be forgotten, which means that they not get updated. Old versions of software tend to be full of known vulnerabilities. Exploit old versions ✓ Some services give an attacker easy access to certain information, they can perform N number of techniques on the operating system. Gain Access: How to identify the processes the process which keep ports open ? ✓ Windows OS : 7/8/10 For Windows operating systems, you can use netstat command, which is included with the OS by default. open command prompt. Run the command: netstat -ano. This will list all the network connections running,listening,established connections on the machine. The last column indicates the process id of the process for the specific network connection. To filter this down using the ‘find’ command. For Instance:if you only want to list the network connections on port 5555, use: type: netstat -ano | find “:5555” Now, that you have identified the process and service that is responding to requests on the specific port or any unsed ports, you would need to confirm that the service is not required or in usage. If you proceed to either configuring the application to stop listening, or stop the service from Windows Services, and marking the service as disabled. The given below screenshot indicates the information for the example. ✓ Linux OS: Red Hat Linux, CentOS, Fedora, openSUSE, Mandrake Linux etc.., open the Terminal. Run the command: . This will list all the network connections running,listening,established connections on the machine. The last column indicates the process id of the process for the specific network connection. netstat -tulpn To filter this down using the ‘find’ command. For Instance: if you only want to list the network connections on port , use: 3306 type: netstat -tulpn | grep :“3306” Depending upon the familiarity, you can use any of these commands (top, ps, pidof, pgrep) for this purpose. Note: Now, that you have identified the process and service that is responding to requests on the specific port or any unsed ports, you would need to confirm that the service is not required or in usage. If you proceed to either configuring the application to stop listening, or stop the service from Linux Services, and marking the service as disabled. The given below screenshot indicates the information for the example. In order to stop daemons in Debian-flavoured Linux distributions, use the following commands to stop any daemons on the server. Ubuntu: service mysqld stop or /etc/init.d/mysqld stop Or To kill the particular process by using the fork command. Find (and ) all listening on a . Killing by the process ID is useful when you want to kill only a specific process. On the other hand, killing by the process name is useful when you want to kill all running instances of a particular program. To get to know more about the kill singal process information.Please, refer kill processes port http://manpages.ubuntu.com/manpages/xenial/man2/kill.2.html pkill - INT process-name sudo kill - 9 PID ✓ You stop a service with the command. Centos: systemctl stop systemctl stop httpd You can also kill a particular process that has been running for a certain period of time on the server with the command -o and -y flags. So, if you want to kill a process that has been running for more than 30 minutes and less than 30 minutes. Eg: killall -o 30m mysql Eg: killall -y 30m mysql more than 30 minutes: Killall -o 30m <process-name> less than 30 minutes: Killall -y 30m <process-name> Abbreviations: Time period s-seconds m-minutes h-hours d-days w-weeks M-months y-years — — — — — — — — Firewall Operations: Centos 6/7 — — — — — — — Firewall Operations: List services 1. List current services: You can check the current running services by specifying the “ — list-services” option in the command. firewall-cmd --list-services  --zone = publicdhcpv6 -client https Firewall Operations: Add services 2. Add service: To add a service by specifying the “ — add-service” option. firewall-cmd --add-service = https --zone = public --permanent 3.Delete Service: firewall-cmd --add-service = https --zone = public --permanent Firewall Operations: List Ports 1. List ports: You can check the current running ports by specifying the “ — list-ports” option in the command. firewall-cmd --list-ports  --zone = public Firewall Operations: ADD port Number 2. Add Port Number: firewall-cmd --add-port = 5555 / tcp --zone = public Firewall Operations: ADD port Numbers 3.Delete Port Number: firewall-cmd --remove-port = 5555 / tcp --zone = public or firewall-cmd --reload firewall-cmd --zone=public --permanent --remove-port= 5555 /tcp — — — — — — — — - Firewall Operations: Ubuntu — — — — — — — 1. Firewall Operations: List services Sudo ufw status Firewall Operations: Add services 2. Add service: To add a service by specifying the “ — add-service” option. sudo ufw allow http Firewall Operations: ADD port Number sudo ufw allow 80 /tcp There are to delete UFW rules, by rule number and another one by specifying the actual rule code. two different ways Method one: sudo ufw status numbered To delete a particular rule number, specific the rule number that allows connections port to use 45009, that is #119. Use the following command to delete the port/service together. sudo ufw delete 119 To delete a rule by specifying the actual rule code. Method Two: sudo ufw delete allow 45009 Disable Firewall: If for any reason you want to stop UFW and deactivate all the rules you can use: sudo ufw disable Enable Firewall: sudo ufw enable (Back to default settings) Reset Firewall: Be aware, Resetting UFW will disable UFW, and also delete all active rules. sudo ufw reset Quote of the day: “ English Proverb Into every life a little rain must fall” — Explanation: English Proverb appreciation We all wish for only the good days, but to appreciate the good day , we also need more difficult ones. The bad times teach us lessons, help us grow, and as stated gives us an for the good times. Always remember that the rain does stop and the sun does shine again. Thanks for reading! Have a pleasant day! Also published at https://medium.com/@gtmars/types-of-tcp-udp-protocol-services-protocol-master-chart-and-windows-linux-ubuntu-centos-server-429b6597a1fa

Insight Into TCP/UDP, Network Vulnerabilities and Defense Approaches

Two-year-old Xenia Rose has already started working towards her dream of being a professional artist, with the launch of her first collection of NFTs. Her mum, Lauren Gilman, a software developer from Suffolk, UK, decided to turn her daughter’s love of drawing and painting into a series of NFTs to hopefully ensure a secure financial future for her budding artist. “Xenia Rose has loved drawing since she was old enough to hold her first crayon. She will happily spend hours drawing and sketching on whatever she can get her hands on. When I got a new iPad, she was hooked and instantly started creating her own digital artwork using the Apple pencil. She gets such pleasure from her art and I want to ensure that she can afford to continue this passion for as long as she wants” explains Lauren. With NFTs becoming more and more popular and some collections changing hands for in excess of £400,000, it is a growing art marketplace that is beginning to achieve mainstream credibility. Lauren says “I have been closely watching the growing popularity of NFTs, but not being an artist myself, thought it was something I would never be able to get involved in. But when Xenia Rose showed a passion for digital art, a light bulb went off in my head and I thought there is no harm in putting her art out there for the world to see.” Xenia Rose’s first collection is called Animals and features an abstract representation of the various pets, farm animals and zoo animals she has seen in her life. Her first ever NFT titled, Tortuse, is based on her pet Horsefield tortoise ‘Norman’. You can view the entire collection here: https://opensea.io/collection/xeniaroseanimals

This 2-Year-Old Artist Has Her Own NFTs

For 2021, went all out for its annual Noonies Awards, making it the biggest Noonies to date. Hacker Noon The theme for the awards can be deemed . Because we had more categories, more sub-categories, more nominees, than ever before, and you guessed it, there will be More more winners too! In case you don’t believe us, here are some stats: for one (or more) of the 4,961 nominees for 2021, 586 Hacker Noon awards across : 6 award categories , , , , , and . Decentralization Gaming Internet Heroes Internet Software Development Technology and a monumental over at 105,122 votes cast noonies.tech The award category honors those individuals and organizations contributing toward a decentralized world, as well as the writers shining a spotlight on decentralization today. Decentralization This category alone had . 22 Awards To see the winners simply visit , pick an award, and discover which name appears at the top. That’s the winner! noonies.tech The will announce some of the top founders, hackers, and makers in all 6 categories. Noonies Winners Annoucement series Decentralization, as an idea and movement, aims to decentralize power and decentralize governance itself. Be it cryptocurrencies, decentralized finance, or decentralized autonomous organizations (DAOs), there are many developers, entrepreneurs, and companies working hard to create the technology that makes decentralization possible. Now, without further delay...Here are all the winners in : Decentralization List of Awards in the Decentralization Category Best Crypto-Journalist What happens on Blockchain stays on the Blockchain - until someone gets hurt. This award recognizes the best crypto-journalists of 2021 and the winner is…. Sergey Golubev Best Crypto-Wallet Not your keys, not your crypto. This award recognizes the best crypto-wallet of 2021 and the winner is…. Guarda Wallet Best Decentralized Exchange Your airdropped coin is not listed on any exchange? Set up a liquidity pool and get trading. This award recognizes the best decentralized exchange of 2021 and the winner is…. DeFiChain Best Source of Crypto-News When you're in crypto, you need to know where the butterfly flapped its wings so that you can go all-in (or cash-out) at the right time. This award recognizes the fountains of news regarding all things crypto and the winner is…. Xenia von Wedel, President of TransformGroup Biggest Blockchain Bro This dude is absolutely crushin' it on the blockchain, bro. 🤑 and the winner is…. Douglas Horn Breakout Blockchain Ethereum gave us smart contracts which gave us self-confessing ETH-killer Blockchains. This award recognizes the Blockchain that is most likely to unseat Ethereum and the winner is…. Telos Centralization Vanquisher of The Year These nominees WILL NOT STOP until decentralization becomes a reality. 😤 and the winner is…. Dominic Ryder Cryptocurrency Podcast of the Year The crypto podcast you actually learn from and enjoy listening to. Decentralize the internet! and the winner is…. The Cryptoshow HackerNoon Dappacious Writer Puritans would still differentiate between what constitutes a dApp and what should be Web3. This award recognizes the best dApp stories on HackerNoon and the winner is…. Igor Ponomarev HackerNoon's Altcoin Champion Shitcoins, Rugpulls, and NGMI - Altcoins have been called a lot of names, from inside and outside the crypto-community. This award recognizes the best coverage of altcoins on HackerNoon and the winner is…. Tran Hung, CEO - UQUID HackerNoon's Biggest BUIDLer of Blockchain Some say, Blockchain, not bitcoin, is where the magic lies. This award recognizes the best Blockchain story on HackerNoon and the winner is…. Douglas Horn, Chief Architect of Telos Blockchain HackerNoon's Bitcoin Crusader Bitcoin can never be turned off and this fact turns on a lot of people on (and at) Twitter. This award recognizes the best bitcoin stories on HackerNoon and the winner is…. Benhodlin HackerNoon's Decentralizer Decentralize Everything was a war-cry of the 2017 ICO Boom. This award recognizes the best decentralization stories on HackerNoon and the winner is…. Douglas Horn HackerNoon's DeFi Degen Did you know that DeFi and its 10000% Daily Gainzzz is the reason behind the end of crypto-winter. This award recognizes the best DeFi stories on HackerNoon and the winner is…. Sergey Baloyan HackerNoon's NFT Wizard NFTs are Schrodinger's baseball card. This award recognizes the best NFT writer on HackerNoon and the winner is…. Christian Kameir HackerNoon's Regulation-Nation Only death and taxes are certain, said the regulator. This award recognizes the best regulation stories on HackerNoon and the winner is…. lamat HackerNoon's Smart Contractor Vitalik Buterin rues the fact that he used the term 'smart contract' when these persistent scripts are neither smart and nor are they contracts. The term now generates millions of dollars every month. This award recognizes the best smart contract stories on HackerNoon and the winner is…. Telos EVM HackerNoon's Top Trading Alpha Provider Stock Markets are for the faint of heart. In crypto, we're either becoming millionaires or applying for an extra shift at McDonalds. This award recognizes the pack leader of the planet of the risk-takers.  and the winner is…. Crypto Fundamentals HackerNoon's Whitehatter Everything that can be hacked will be hacked. Everything that cannot be hacked shall also get hacked. This award recognizes the best HackerNoon stories on preventing crypto-hacks, rug-pulls, and such shenanigans and the winner is…. Master Mind Content Memecoin of 2021 Much Wow, memes, pepes, and giggles. Memecoins have unseated many a 'solid' project in terms of market cap, for the lulz. This award recognizes the best memecoin of 2021 and the winner is…. Shiba Inu Token MVP of Web3 Web3 is the inevitable death of Facebook. This is why Mark Z. is looking at metaverses. This award recognizes those Web3 technologies that are most likely to ensure our online privacy and the winner is…. Mariano Conti Naval Ravikant of Crypto Some folks make so much sense that it is scary, good, and reassuring at the same time. This award recognizes the dropper of wisdom from the years to come and the winner is…. Ryan Selkis More Information: If you’re a winner, please answer ! If you’re a reader, participant, or just a curious individual, consider answering one of our other interviews . this interview here Read about the Noonies . To see all of the winners you may visit , pick any award, and view the name that appears at the top. here this site Or follow for posts with the list of names released over the course of the week of February 14, 2022. this account The will announce some of the top founders, hackers, and makers in all 6 categories. Noonies Winners Annoucement series Thank you to all of our sponsors! We truly appreciate your contribution to the tech world and thus the future! The Noonies Awards are sponsored by: , , and hosted by: Bybit Avast TECH Domains HackerNoon This post was written by Zaeem Shoaib. If you have any questions or concerns or would like to report a discrepancy please email ellen@hackernoon.com.

#Noonies2021 Awards: Winners in the Decentralization Category 

30 Web Design Trends To Look For in 2021

In this article on “14 Steps to Install kubernetes on Ubuntu 18.04 and 16.04” we are going to create Kubernetes cluster along with kubeadm on Ubuntu 18.04 (The same steps can be used for the Ubuntu 16.04 as well) kubeadm is command line tool to interact with kubernetes cluster. Kubeadm relies on fast deployment feature of Docker and running the system services of kubernetes master and etcd server as container. We are going to use two nodes Master node Worker node Prerequisites Reading time is about 20 minutes Vagrant 2.2.7 or latest – For installationi nstruction click here VM VirtualBox – For installation instruction click here As a minimum requirement for kubernetes installation we need – Step 1 – Start your vagrant box Master Node – 2 cpus, 2 GB Memory Worker Node – 1 cpu, 1 GB Memory Use following Vagrantfile to spin up your vagrant box Vagrant.configure( ) |config|
  config.vm.define |master|
    master.vm.box_download_insecure = master.vm.box = master.vm.network , : master.vm.hostname = master.vm.provider |v|
      v.name = v.memory = v.cpus = end
  end

  config.vm.define |worker|
    worker.vm.box_download_insecure = worker.vm.box = worker.vm.network , : worker.vm.hostname = worker.vm.provider |v|
      v.name = v.memory = v.cpus = end
  end

end "2" do "master" do true "hashicorp/bionic64" "private_network" ip "100.0.0.1" "master" "virtualbox" do "master" 2048 2 "worker" do true "hashicorp/bionic64" "private_network" ip "100.0.0.2" "worker" "virtualbox" do "worker" 1024 1 SSH into the master node Step 2 – Update host files on both master and worker node master node – $ vagrant ssh master Add host entry for master as well as worker node vagrant@master:~$ sudo vi /etc/hosts master.jhooq.com master worker.jhooq.com worker 100.0 .0 .1 100.0 .0 .2 Test the worker node by sending from master [vagrant@master ~]$ ping worker
PING worker.jhooq.com ( ) ( ) bytes data. bytes worker.jhooq.com ( ): icmp_seq= ttl= time= ms bytes worker.jhooq.com ( ): icmp_seq= ttl= time= ms 100.0 .0 .2 56 84 of 64 from 100.0 .0 .2 1 64 0.462 64 from 100.0 .0 .2 2 64 0.686 Test the master node by sending from worker [vagrant@worker ~]$ ping master
PING master.jhooq.com ( ) ( ) bytes data. bytes master.jhooq.com ( ): icmp_seq= ttl= time= ms bytes master.jhooq.com ( ): icmp_seq= ttl= time= ms 100.0 .0 .1 56 84 of 64 from 100.0 .0 .1 1 64 0.238 64 from 100.0 .0 .1 2 64 0.510 Step 3 – Install Docker on both master and worker node You need to install Docker on both the node. So run the following installation command on both the nodes [vagrant@master ~]$ sudo apt-get update

[vagrant@master ~]$ sudo apt install docker.io Enable and start docker vagrant@master:~$ sudo systemctl enable docker
Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service.

[vagrant@master ~]$ sudo systemctl start  docker Check the docker service status [vagrant@master ~]$ sudo systemctl status docker

● docker.service - Docker Application Container Engine
   Loaded: loaded ( systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu : : UTC; s ago
     Docs: https: /lib/ 2020 -04 -23 19 10 59 4 //docs.docker.com We need to disable firewall as well as swapping on master as well as worker node. Because to install kubernetes we need to disable the swapping on both the nodes Step 4 – Disable the firewall and turnoff the “swapping” vagrant@worker:~$ sudo ufw disable
Firewall stopped and disabled on system startup

[vagrant@worker ~]$ sudo swapoff -a Step 5 – Install “apt-transport-https” package To download the kubernetes and its public we need to install “apt-transport-https” package on both master as well as worker node vagrant@master:~$ sudo apt-get update && sudo apt-get install -y apt-transport-https Step 6 – Download the public keys We need to have the public keys for accessing packages on Google Cloud. So run the following command to get the public keys on both master as well as worker node vagrant@worker:~$ curl -s https: OK //packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add - Step 7 – Add kubernetes repo As a next step we need to add the kubernetes repo to both master as well as worker node vagrant@worker:~$ sudo bash -c 'echo "deb http://apt.kubernetes.io/ kubernetes-xenial main" > /etc/apt/sources.list.d/kubernetes.list' Step 8 – Install kubernetes Now after adding the kubernetes repo we need to install the kubernetes on both mater as well as worker node vagrant@master:~$ sudo apt-get update && sudo apt-get install -y kubelet kubeadm kubectl Step 9 – Enable and Start kubelet Alright now we have installed the kubernetes, now we need to enable the kubelet support for both master as well worker node [vagrant@master ~]$ sudo systemctl enable kubelet

[vagrant@master ~]$ sudo systemctl start kubelet Step 10 – Initialize the kubernetes cluster Okay now we have reach to point where we have done all the prerequisite for initializing the kubernetes cluster. Let’s run the kubernetes initialization command on only on master [vagrant@master ~]$ sudo kubeadm init --apiserver-advertise-address= --pod-network-cidr= / 100.0 .0 .1 10.244 .0 .0 16 Note down kubeadm join command which we are going to use from worker node to join the master node using token. sudo kubeadm join : --token g2bsw7 xr3bqc21eqyc6r7 --discovery-token-ca-cert-hash sha256: b2b0608b9300b3342a8d0a0e9204c8fc74d45b008043a810f94e4f1fb8861f 100.0 .0 .1 6443 .5 39 Step 11 – Move kube config file to current user (only run on master) To interact with the kubernetes cluster and to use kubectl command, we need to have the kube config file with us. Use the following command to get the kube config file and put it under working directory. [vagrant@master ~]$ mkdir -p $HOME/.kube
[vagrant@master ~]$ sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
[vagrant@master ~]$ sudo chown $(id -u):$(id -g) $HOME/.kube/config Step 12 – Apply CNI from kube-flannel.yml(only run on master) After the master of the cluster is ready to handle jobs and the services are running, for the purpose of making containers accessible to each other through networking, we need to set up the network for container communication Get the CNI(container network interface) configuration from flannel [vagrant@master ~]$ wget https: //raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml Note – But since we are working on the VMs so we need to check our Ethernet interfaces first. Look out for the Ethernet i.e. eth1 which has a ip address 100.0.0.1(this is the ip address which we used in vagrant file) [vagrant@master ~]$ ip a s : lo: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:00:27:bb:14:75 brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:00:27:fb:48:77 brd ff:ff:ff:ff:ff:ff
    inet 100.0.0.1
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> 1 2: eth0: < > LOOPBACK,UP,LOWER_UP Now we need to add the extra args for eth1 in kube-flannel.yml [vagrant@master ~]$ vi kube-flannel.yml Searche for – “flanneld” In the args section add : – –iface=eth1 - --iface=eth1
        args:
        - --ip-masq
        - --kube-subnet-mgr
        - --iface=eth1 Apply the flannel configuration vagrant@master:~$ kubectl apply -f kube-flannel.yml podsecuritypolicy.policy/psp.flannel.unprivileged created
clusterrole.rbac.authorization.k8s.io/flannel created
clusterrolebinding.rbac.authorization.k8s.io/flannel created
serviceaccount/flannel created
configmap/kube-flannel-cfg created
daemonset.apps/kube-flannel-ds-amd64 created
daemonset.apps/kube-flannel-ds-arm64 created
daemonset.apps/kube-flannel-ds-arm created
daemonset.apps/kube-flannel-ds-ppc64le created
daemonset.apps/kube-flannel-ds-s390x created Step 13 – Join worker nodes to master(only run on worker) In the Step 10 we generated the token and kubeadm join command. Now we need to use that join command from our worker node vagrant@worker:~$ sudo kubeadm join : --token g2bsw7 xr3bqc21eqyc6r7     --discovery-token-ca-cert-hash sha256: b2b0608b9300b3342a8d0a0e9204c8fc74d45b008043a810f94e4f1fb8861f 100.0 .0 .1 6443 .5 39 W0423 : : join.go: ] [preflight] WARNING: JoinControlPane.controlPlane settings will be ignored when control-plane flag is not set.
[preflight] Running pre-flight checks
	[WARNING IsDockerSystemdCheck]: detected the Docker cgroup driver. The recommended driver is . Please follow the guide at https: [preflight] Reading configuration the cluster...
[preflight] FYI: You can look at config file [kubelet-start] Downloading configuration the kubelet the ConfigMap the kube-system namespace
[kubelet-start] Writing kubelet configuration to file [kubelet-start] Writing kubelet environment file flags to file [kubelet-start] Starting the kubelet
[kubelet-start] Waiting the kubelet to perform the TLS Bootstrap...

This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed the secure connection details.

Run on the control-plane to see node join the cluster. 19 27 00.344480 18268 346 "cgroupfs" as "systemd" //kubernetes.io/docs/setup/cri/ from this with 'kubectl -n kube-system get cm kubeadm-config -oyaml' for from "kubelet-config-1.18" in "/var/lib/kubelet/config.yaml" with "/var/lib/kubelet/kubeadm-flags.env" for of new 'kubectl get nodes' this Step 14 – Check the nodes status(only run on master) To check the status of the nodes use [vagrant@master ~]$ kubectl get nodes NAME     STATUS   ROLES    AGE   VERSION
master   Ready    master m   v1 worker   Ready    <none> s   v1 26 .18 .2 63 .18 .2 Summary So this was our beginner tutorial which involves around – 14 Steps to Install kubernetes on Ubuntu 18.04 and 16.04. With that we can conclude what we have achieved – Congratulations we have successfully installed kubernetes on Ubuntu 18.04 After installing kubernetes we are successfully join the worker nodes with master.

How to Set Up a Kubernetes Cluster on Ubuntu 20.04/18.04/16.04 in 14 Steps

Kubernetes in the leading Container Orchestration platform that allows you to apply fast and streamlined infrastructure workloads using a declarative API. In this tutorial, we are going to follow a step-by-step guide for signing in with Platform9 Managed Kubernetes Platform, creating a new cluster and deploying an example application. Then we will see how to scale-up/down our application instances and how to roll out a new updated instance of our app. Let’s get started. Sign-up To gain the benefits of Platform9, we need to register a new account. Head over to Sign up Page located here: SignUp Page Fill in your details in the Form: You will be asked to provide a verification code sent to your email, and a secure password: Platform9 Managed Kubernetes (PMK) provides us with a pure-play open source Kubernetes delivered as a SaaS managed service. Once there, you will be presented with the Dashboard Screen. Initially, we have no cluster configured, so we need to create one. Setting up A Cluster First, lets get familiarized with the possible pages as shown on the sidebar section: Infrastructure: This section lists an overview of all the clusters, nodes and cloud providers. Pods/Deployments/Services: This section lists all pods, deployments and services.Storage Classes: This section lists all the storage classes. Namespaces: This section lists all cluster namespaces. RBAC: This section shows information about configured RBAC roles, and role bindings. API Access: This section indicates information about API access tokens and kubeconfig settings. Users/Roles: This section displays information about users and defined roles. Now that you are familiar with the UI Dashboard, let’s create a new K8s cluster where we are going to deploy an example application container. Click on the Dashboard Link and then click on Create Your Cluster: On the next screen, choose the Cloud Provider. Here we can select BareOS, which can be a local or remote VM: Follow the instructions to prepare some Kubernetes nodes. Pay attention to the following: For this tutorial I used two Scaleway Instances and bootstrapped a cluster node on each VM. We can do the same process using VirtualBox using Ubuntu Xenial images. Just make sure you have the hardware requirements. We used the following commands to prep each node: $ pf9ctl cluster prep-node -u root -i <NodeIP> -s <sshKey> If the node preparation progress gets stuck at 95%, then enter CTRL+C to unblock it. It should then show the success message in the console. Note: Once you have prepared the instances, go into the UI again and refresh the screen. After a while you will be able to proceed with the master and the worker selection screens, as depicted in the images below: At the end you should be having a basic cluster configured and prepped, and you will be able to see the Node Stats and system pods as shown below: After that we are ready to issue our first deployment. Issuing a Deployment Once we have our cluster ready, we can download the kubeconfig file and use it as our context. This way, we can use the kubectl CLI tool as well, for the remainder of the tutorial. Navigate to the API Access section and click on the cluster name under the Download kubeconfig section. This will download a yml file. We need to use this as the cluster config: In a new shell, export the KUBECONFIG environmental variable pointing to the downloaded file location: $ KUBECONFIG=$(pwd)/test.yaml export then issuing the get-clusters command will show us the demo cluster: $ kubectl config get-clusters
NAME
test Now lets see how we can issue our first deployment. Click on and select . Pods/Deployments Deployment Fill in the form by selecting the cluster and the default namespace. New Resource For the Deployment Description we can use a simple Node.js Application as an example. Here is the spec: apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: nodejs-deployment
spec:
  selector:
    matchLabels:
      app: nodejs
  replicas: template:
    metadata:
      labels:
        app: nodejs
    spec:
      containers:
      - name: nodejs
        image: joerx/express-hello-src:latest
        ports:
        - containerPort: livenessProbe:
          httpGet:
            path: headers
            port: initialDelaySeconds: periodSeconds: 1 3000 /headers
            port: 3000
          initialDelaySeconds: 30
          periodSeconds: 30
        readinessProbe:
          httpGet:
            path: / 3000 15 3 Here is a small breakdown of the above specification: apiVersion: We specified the version of the deployment spec here. I used kind: We specified a deployment type.metadata: We defined a name for our deployment as nodejs-deployment.spec: here we define our deployment specification. We assign a label, a label selector, one replica instance and the container image information. We also added some health probes to detect status. this reference site When saved, on the dashboard we can see the phases of the deployment. If you click on the name, you should be redirected to the Kubernetes Dashboard. Once it’s ready, though, we cannot directly access it because the server is exposed only inside the cluster. We need to add a service specification to expose it in public. We can use the Button to do that. Services->Add Service Here is the spec: apiVersion: v1
kind: Service
metadata:
  name: nodejs-service
spec:
  selector:
    app: nodejs
  ports:
    - protocol: TCP
      port: type: NodePort 3000 Here we expose the Node.js application using a service named and assigns TCP port within a range 30000-32767 with the container port 3000, which our application runs. The key thing to note is the , which will expose the port in the node public IP address. nodejs-service type: NodePort Now in order to check our application, we need to find the actual IP of the VM node. In this example mine is: 51.158.108.219, so we need to open a browser link to the following path: http://51.158.108.219:30180/ Indeed, as you can see in the following picture, the server has responded with our IP address: Scaling a Deployment The current deployment spins up one instance of the Application. If we want to scale it up, we can use the Kubectl CLI tool; or, we can use the Kubernetes UI, instead. If we click on the deployment link, it will redirect us to the Kubernetes UI. The first time it will ask for a token, which is present inside the file we downloaded earlier. kubeconfig yml We just only need to select the deployment in the Deployments list on the right-hand side with the three dots. Select Scale and then in the model, change the number from 1 to 3: After that, we can see the pods increasing from one to three in the dashboard: Note that when using this approach, there are some limitations, as we currently have only two nodes and three instances; so, we are able to reach only two out of three pods. In subsequent tutorials we can see how different types of services can overcome this limitation. Deploying a new version of the App Similarly, if we wanted to deploy a newer version of the Application, we just need to change the deployed image reference to point to a new image. Using the kubectl command, this can be done as easy as issuing the following command: $ kubectl set image deployment <deployment> <image> --record = < > container For example: $ kubectl set image nodejs-deployment  nodejs=joerx/express-hello-src:latest Before we do that though, it’s important to define a so that we can limit the number of images that are being replaced at the same time. We need to add the following section in the deployment spec section: Rolling update strategy strategy:
    type: RollingUpdate
    rollingUpdate:
      maxSurge: maxUnavailable: 1 1 Here we want a maximum of one pod unavailable and a maximum of one extra pod update at the same time. This effectively means that there will be, at most, four pods during the update process, as we currently have three pods running (3 + 1 with the new version) Also note one more thing – we started with the following image: joerx/express-hello-src:latest Ideally, we should always be using a version tag. For example: joerx/express-hello-src: 1.0 .0 Then, when we want to deploy the next version – such as 1.1.0 – we can set the following docker image: joerx/express-hello-src: 1.1 .0 Any subsequent updates should follow this convention. I leave it as an exercise to the reader to perform a rolling update of an image from an older version to a newer one. Overview and next steps In this tutorial, we walked through the process of signing up with Platform9, setting up our own Kubernetes cluster and issuing an example deployment. We also learned how to navigate to the Kubernetes dashboard, scale up the deployment and expose our app via a service specification.

Get your First Container Up on Kubernetes Using the Free Version of Platform9 Managed Kubernetes

Learning AI if You Suck at Math — P3 — Building an AI Dream Machine or Budget Friendly Special

[A How To Guide] Planning the Technology Stack for an Event Sourcing Project

Steps to initiate replica set configuration in an existing standalone MongoDB cluster. Update Primary cluster Configuration: Create a key file for authentication in an existing MongoDB cluster. $ openssl rand -base64 756 > <path-to-keyfile>
$ chmod 400 <path-to-keyfile>
$ chown mongodb:mongodb <path-to-keyfile> 2. Add security and replication configuration in /etc/mongod.conf file. $ vim /etc/mongod.conf
security:
  keyFile: <path-to-keyfile>
replication:
  replSetName: <replicaSetName> <a href="https://medium.com/media/d560e3290364ee8096219d8184109e0f/href">https://medium.com/media/d560e3290364ee8096219d8184109e0f/href</a> Refer this link for more details: Enforce Keyfile Access Control in a Replica Set - MongoDB Manual 3. Restart MongoDB in existing MongoDB cluster. $ systemctl restart mongod
$ systemctl status mongod In case of error please refer file and try to fix on the basis of error logs. /var/log/mongodb/mongod.log 4. Login in mongo with admin credentials. $ mongo -u <username> -p <password> — authenticationDatabase admin
$ use admin 5. Initiate replica set configuration. $ rs.initiate() 6. Check the status and configuration of the replica set: $ rs.conf()
$ rs.status() 7. Now, the existing cluster becomes . Primary Create Secondary Cluster: Create a Machine with the required specifications in the cloud platform. SSH in the machine using the command: $ ssh <Cluster_IP>
$ sudo su 3. Install MongoDB in the new machine. For compatibility, The version of MongoDB should be the same as the version in the existing Primary cluster. These are the Command to install MongoDB in new compute engine. Please change the version of MongoDB based on your requirement: $ sudo apt-key adv — keyserver hkp://keyserver.ubuntu.com:80 — recv 2930ADAE8CAF5059EE73BB4B58712A2291FA4AD5
$ echo “deb [ arch=amd64,arm64 ] https://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.2 multiverse” | sudo tee /etc/apt/sources.list.d/mongodb-org-3.6.list
$ sudo apt-get update
$ sudo apt-get install -y mongodb-org 4. Copy same configuration file and in new machine from existing primary MongoDB cluster. /etc/mongod.conf key file <path-to-keyfile> change the permission of the key file using these commands: $ chmod 400 <path-to-keyfile>
$ chown mongodb:mongodb <path-to-keyfile> 5. start mongod in new MongoDB cluster. $ systemctl start mongod
$ systemctl status mongod In case of error please refer file and try to fix on the basis of error logs. /var/log/mongodb/mongod.log Add the new machine as a replica in an existing primary cluster: Login in Primary cluster: $ mongo -u <username> -p <password> — authenticationDatabase admin
$ use admin 2. Add the new machine in Primary MongoDB: $ rs.add({host: <Cluster_IP:27017>, priority: <priority>, votes: <votes>}) 3. Check status and configuration: $ rs.conf()
$ rs.status() 4. Login in the new machine and verify about replication: $ mongo -u <username> -p <password> This machine will become as secondary and start replicating all data. Verify replica set connection with JavaScript: sample code to verify replica set configuration using JavaScript. <a href="https://medium.com/media/2757375a31f78f94bb44a81dbc25e908/href">https://medium.com/media/2757375a31f78f94bb44a81dbc25e908/href</a>

How to setup replicaSet in standalone MongoDB cluster.

If you are here, you are interested in topics such as DevOps , Continuous Processes , and Infrastructures , at least I hope so! This article aims to provide a high-level, simple and practical explanation of what it is Vagrant and how you can use it to improve your workflow. 👨‍💻_@_ 👨‍🏫_at the_ 🖥_, a_ masters level course of the “Master Degree in Information Systems and Computer Engineering” and “Master Degree in Telecommunications and Informatics Engineering” . I’m currently a teacher assistant Técnico Lisboa , and I’m working closely with Dr. Professor Rui Cruz It Infrastructure Management and Administration @ Técnico Lisboa main responsible for the “ ” and “ ” sections. The contribution from Dr. Professor Rui Cruz to this article is enormous, being him the main responsible Setting Up The Experiment So, what is Vagrant? In a very simple way, Vagrant is that is used for building and distributing virtual environments. This means, essentially, that it allows you to manage and share pre-configured virtual machines. an open source project 🔭 Use case #1: Focusing on your task As a developer, have you already spent too much time setting your environment? Vagrant makes it really easy to manage virtual boxes. An already all-in-one virtual machine with all the software and dependencies installed is a great way to make developers focused on their tasks. One just needs to create an optimal virtual box, once, and then it can be distributed to collaborators. No need for setting up the environment, as it should be already set up! In short, you just need to run the machine and focus on the task on hands. 📈 Use case #2: Improving the workflow As a developer, have you already spent too much time fixing bugs that happen on production, but not in the development environment? Firstly, one should follow good workflow practices, such as the ones referenced by , by . Secondly, we can take the next step in our automation process: having the exact same environment, both in development and production (and the intermediary ones). If this is accomplished, the probability of the production app crashing due to an error that was not spot on the development environment is very little, because the environments are the same. this insightful article Peter Murray In short, you can develop without being afraid of errors coming from dependencies and installed software. ⭐️ Use case #3: Distribution Have you spent some time writing extensive documentation on how to do a setup of a project? Sometimes it can be frustrating, as there may be lots of aspects to take care: environment variables, software, and specific configurations. If you have the need for a pre-configured environment, this tool will help you. By packing everything you need on a virtual machine and distributing it, you have done work that others don’t need to (uselessly) replicate. How does it work? According to : Vagrant Environments managed by Vagrant can run on local virtualized platforms such as VirtualBox or VMware, in the cloud via AWS or OpenStack, or in containers such as with Docker. Vagrant provides the framework and configuration format to create and manage complete portable development environments. These development environments can live on your computer or in the cloud, and are portable between Windows, Mac OS X, and Linux. In a nutshell, Vagrant manages the environments, and uses, for example, VirtualBox to provide (launch) the machines. Scripts that run after the machines are launched can be configured through several provisioners such as the , , and . Provisioners are meant to leverage provisioning (installing dependencies), automation, configuration management, and orchestration. This meets the DevOps way of thinking and working. shell Terraform Chef Ansible The following scheme helps us visualize how vagrant works and how it works. Source: https://www.softqubes.com/blog/introduction-of-vagrant-development/ The user creates a Vagrantfile, which is a declarative file (written in Ruby) that describes the type of machine needed, as well as how to configure and provision that machine. The user uses Vagrant to execute the Vagrantfile. Vagrant uses VirtualBox as a provider. It can also use other providers. The machine is up. Vagrant invokes a provisioner to configure the machine. The provisioner provisions the machine. It can be a simple shell script or Ansible, for example. One can access the deployed machine by ssh. That’s it. You can manage and launch virtual machines with a few commands. And its complexity is as much as you want. Enough theory, let’s do it! Let’s get to work, ladies and gentleman. For demonstration purposes, I will follow the first Lab Guide of First, we need to install the required tools to run Vagrant. After that, we will launch a machine. Mininet allows us to create virtual networks, running real kernel and application code. It Infrastructure Management and Administration course, by Professor Rui Cruz. Mininet Setting Up In this section, we are going to perform the setup for Windows, Linux and mac OS. Windows The recommended Package Manager for Microsoft Windows is . Chocolatey To install Chocolatey, open a privileged (i.e. administrative) Windows Command Prompt (cmd.exe) and execute: @"%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin" Now, install the following dependencies through Chocolatey: C:\> choco install wget C:\> choco install git -params “ /GitAndUnixToolsOnPath “ C:\> choco install virtualbox C:\> choco install vagrant C:\> choco install xming Make sure that git executable file path is on the . PATH environment variable In order for xming (an XWindows server) to work, as we are going to need it later, add the environment variable called , with the value . DISPLAY localhost:0.0 Apple macOS The recommended Package Manager for macOS is Homebrew, similar the Linux aptget or yum http://brew.sh. If you do not have XCode installed then open Terminal and at the shell prompt type the following: :~$ xcode -select -- install To install , at the shell prompt paste the script (starting at the ruby invocation) and press ENTER: Homebrew :~$ /usr/bin/ ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" When it’s done, the shell prompt will say that the installation was successful, and ask you to run brew doctor. Do as it suggests: :~$ brew doctor This will make Homebrew inspect your system and make sure that everything is set up correctly. :~$ brew install wget :~$ brew install git :~$ brew cask install virtualbox :~$ brew cask install vagrant :~$ brew cask install xquartz Linux To install the other packages open a Terminal and issue the following commands. :~$ sudo apt -get install git Please note that for latest distributions of Ubuntu, a careful install of VirtualBox is required as the package architecture has to match the Linux kernel architecture. Additionally, the VirtualBox package in Ubuntu may have some issues when running in RAM-constrained environments. For that purpose, you need to ensure that you have the adequate sources referenced for your kernel architecture. Start by editing the sources list issuing the following command: :~$ sudo nano/etc/apt/sources.list Add the following line to the list (exemplified for 16.04 ’Xenial’ kernel): deb http://download.virtualbox.org/virtualbox/debian xenial contrib According to your distribution, replace ’xenial’ by ’vivid’, ’utopic’, ’trusty’, etc. You also need to add and register the Oracle public key (combined command): :~$ wget -q https://www.virtualbox.org/download/ oracle_vbox_2016.asc -O- | sudo apt-key add - :~$ wget -q https://www.virtualbox.org/download/ oracle_vbox.asc -O- | sudo apt-key add - Now you can add Virtualbox: :~$ sudo apt -get update:~$ sudo apt -get install virtualbox -5.2 For Vagrant, there is still an issue and we need to get the latest version (not in Ubuntu repository) by downloading the package from the and then issuing the following command (from the downloads folder, adapt to your version): Vagrant website :~$ wget https://releases.hashicorp.com/vagrant/2.1.5/ vagrant_2.1.5_x86_64.deb:~$ dpkg -i vagrant_2.1.5_x86_64.deb The Experiment: Create a folder called mininet and enter it, as we are using the . mininet box :~$ vagrant box add mininet ktr/ This will create a box with the downloaded image from vagrant.org. Now, let’s create a Vagrantfile containing our box: :~$ vagrant init ktr/mininet The above command will fetch an already prepared Mininet system in an Ubuntu OS. Without the comments, this is the Vagrantfile created: $script = <<-SCRIPT

SCRIPT Vagrant.configure("2") do |config|config.vm.box = "ktr/mininet" end config.vm.provision "shell", inline: $script Vagrant.configure sets the Vagrantfile version, while config.vm.box sets the box to be used (the one we downloaded). The script is going to run after the machine is launched. Congratulations! You are almost there. Now, we launch the machine: :~$ vagrant up --provider virtualbox --provision This phase may take up a few minutes, depending on the speed of the host system, with an output similar to the following: Bringing machine 'default ' up with 'virtualbox ' provider ... ==> default : Checking if box 'ktr / mininet ' is up to date ... ==> default : Clearing any previously set forwarded ports ... ==> default : Clearing any previously set network interfaces ... ==> default : Preparing network interfaces based on configuration ... default : Adapter 1: nat ==> default : Forwarding ports ... default : 22 => 2222 ( adapter 1) ==> default : Booting VM ... ==> default : Waiting for machine to boot . This may take a few minutes ... default : SSH address : 127.0.0.1:2222 default : SSH username : vagrant default : SSH auth method : private key ==> default : Machine booted and ready ! ==> default : Checking for guest additions in VM ... default : Guest Additions Version : 4.3.10 default : VirtualBox Version : 5.0 ==> default : Mounting shared folders ... Also, you will see the log coming from the provision script. Next, we will establish a session with the system using the following command: :~$ vagrant ssh The session is established and we will get the machine prompt similar to the following: Welcome to Ubuntu 14.04.4 LTS (GNU / Linux 3.13.0 -87 - generic x86_64 ) Last login : Sun Sep 20 22:50:28 2017 from 10.0.2.2 vagrant@mininet :~$ A very simple test can then be performed to verify that all is working correctly by issuing the command ’ ’ at the mininet shell prompt, to create a simple network topology of two hosts (h1, h2) and a switch (s1): sudo mn vagrant@mininet :~$ sudo mn *** Creating network *** Adding controller *** Adding hosts : h1 h2 *** Adding switches : s1 *** Adding links : (h1 , s1) (h2 , s1) *** Configuring hosts h1 h2 *** Starting controller c0 *** Starting 1 switches s1 ... *** Starting CLI: mininet > From this point we can issue the command ’ ’ to verify if we have connectivity between the hosts: pingall mininet > pingall *** Ping : testing ping reachability h1 -> h2 h2 -> h1 *** Results : 0% dropped (2/2 received ) With the command ’ ’ we can verify how the nodes are connected, i.e., host1 is connected by its eth0 port to the switch1 on eth1 port, etc.: net mininet > net h1 h1 - eth0 :s1 - eth1 h2 h2 - eth0 :s1 - eth2 s1 lo: s1 - eth1 :h1 - eth0 s1 - eth2 :h2 - eth0 c0 Issuing the command ’ ’ we can see the IP addresses of the hosts (10.0.0.1 and 10.0.0.2): dump mininet > dump <Host h1: h1 - eth0 :10.0.0.1 pid =1708 > <Host h2: h2 - eth0 :10.0.0.2 pid =1712 > <OVSSwitch s1: lo :127.0.0.1 , s1 - eth1 :None ,s1 - eth2 : None pid =1717 > <Controller c0: 127.0.0.1:6633 pid =1701 > To end the Mininet emulation we use the command ’exit’. mininet > exit We can now exit the session: vagrant@mininet :~$ exit logout Connection to 127.0.0.1 closed . In order to stop the Virtual Machine and to verify the global state of all active Vagrant environments on the system, we can issue the following commands: :~$ vagrant halt ==> default : Attempting graceful shutdown of VM ... :~$ vagrant global-status Confirm that the status of the VM is . powered off Wrapping up You know understand what Vagrant is, how to set up a simple Vagrant file, how to launch a machine and how to use it. 💯 Congratulations! You reached the end! 🦄 Next steps: Cheers, Keep Rocking 💪If you enjoyed this article, please subscribe to my mailing list.Here 👇. It would mean a lot.

Stories, News & Mentions about XENIA

Xenia’s Stories on HackerNoon