CNCF to Host Vitess



  • Today, theCloud Native Computing Foundation (CNCF)Technical Oversight Committee (TOC) voted to acceptVitess as the 16th hosted project, alongside Kubernetes, Prometheus, OpenTracing, Fluentd, Linkerd, gRPC, CoreDNS, containerd, rkt, CNI, Envoy, Jaeger, Notary, TUF and Rook. Vitess has been accepted as an incubation-level project, under theCNCF Graduation Criteria v1.0.

    The TOC:undefined:’:undefined:s Graduation Criteria provides every CNCF project an associated maturity level of either inception, incubating or graduated. As an incubating project, Vitess must document it is being used successfully in production by at least three independent end users, have a healthy number of committers and demonstrate a substantial ongoing flow of contributions.

    Originally created as an internal solution by YouTube to handle scaling for massive amounts of storage, Vitess is a database orchestration system for horizontal scaling of MySQL through generalized sharding. By encapsulating shard-routing logic, Vitess allows application code and database queries to remain agnostic to the distribution of data onto multiple shards. With Vitess, organizations can even split and merge shards as needs grow, with an atomic cutover step that takes only a few seconds. Companies like BetterCloud, Flipkart, Quiz of Kings, Slack, Square Cash, Stitch Labs and YouTube are using Vitess across various stages of production and deployment. Organizations including Booking.com, GitHub, HubSpot, Slack, and Square are also active contributors to the project.

    :undefined:“:undefined:Slack is in the midst of a major migration of the MySQL infrastructure at the core of our service, driven by the need for an architecture that scales to meet the growing demands of our largest customers and features under the pressure to maintain a stable and performant service that executes billions of MySQL transactions per hour, said Michael Demmer, Senior Staff Engineer at Slack. :undefined:“:undefined:We needed a solution that would offer a familiar full featured SQL interface, and wanted to continue to use MySQL as the backing store to maintain our operations knowledge and comfort level. Vitess is a natural choice for this purpose and has served us well so far.:undefined:”:undefined:

    Vitess has been under development since 2010. The earliest version was a connection proxy that helped to buy some headroom, but over time the features evolved, while the tools and servers grew to be more efficient, fault tolerant, and manageable. This iterative journey led to what Vitess has become today: a distributed, cloud-based storage solution that exhibits some of the best properties of a relational database.

    :undefined:“:undefined:Faced with rapid organic and internal growth at YouTube, we had to come up with something that would leap ahead of the curve instead of just fighting fires. When we finally built the initial feature list for Vitess, it was obvious that we were addressing problems that are common to all growing organizations,:undefined:”:undefined: said Sugu Sougoumarane, CTO at PlanetScale Data and Co-creator of Vitess. :undefined:“:undefined:Our collaboration with Kubernetes over the last two years means anyone can now run Vitess the way YouTube does: dynamically scaled and scheduled in a container cluster. We:undefined:’:undefined:re excited to work with the CNCF to expand the capabilities of Vitess even further.:undefined:”:undefined:

    Main features:

    • Combines important MySQL features with the scalability of a NoSQL database
    • Enables MySQL to run in the cloud
    • Cloud-native functionality such as support for automatic failover/recovery, replication and rolling upgrades
    • Vertical and horizontal sharding support, and virtually seamless dynamic re-sharding
    • Multiple sharding schemes, with the ability to plug-in custom ones
    • Query routing, rewriting and sanitization, blacklisting, streaming, and de-duping
    • Master management tools (handles reparenting)
    • Performance analysis tools

    Technical Specs:

    • Backend components implemented in Go
    • Continuously tested against Ubuntu 14.04 (Trusty) and Debian 8 (Jessie). Other Linux distributions should work as well
    • Supports MySQL 5.6, MariaDB 10.0, and any newer versions
    • VTGate server is the main entry point applications use to connect to Vitess
    • Supports data backups to either a network mount (e.g. NFS) or to a blob store

    :undefined:“:undefined:To build successful cloud native applications, developers have to consider new ways of managing storage,:undefined:”:undefined: said Chris Aniszczyk, COO of Cloud Native Computing Foundation and Vice President of Developer Relations at The Linux Foundation. :undefined:“:undefined:Vitess is a fantastic example of bridging the existing popular MySQL database and scaling it in a cloud native fashion.:undefined:”:undefined:

    The open source Vitess projectruns best in a containerized environment. With Kubernetes and Google Kubernetes Engine as the container cluster manager, it:undefined:’:undefined:s now a lot easier to get started. In this environment, Vitess provides a MySQL storage layer with improved reliability, scalability, and manageability. Kubernetes handles scheduling onto nodes in a compute cluster, actively manages workloads on those nodes, and groups containers comprising an application for easy management and discovery.Also with Kubernetes, Vitess even becomes agnostic to the underlying choice of cloud platform, providing cloud portability with no vendor lock-in.

    Notable Milestones:

    • 105 contributors
    • 5,413 GitHub stars
    • 15 releases
    • 13,733 commits
    • 707 forks

    :undefined:“:undefined:A big advantage of cloud solutions is easy horizontal scalability, but when it comes to stateful systems such as databases, the problem is that application complexity and operational overhead tend to scale up along with the number of instances,:undefined:”:undefined: said Brian Grant, TOC representative and project sponsor. :undefined:“:undefined:A cloud-native solution like Vitess abstracts the complexity of horizontal scalability from both application developers and database operators. We:undefined:’:undefined:re thrilled to welcome Vitess as a CNCF project as we continue to enable more classes of workloads in cloud-native environments.:undefined:”:undefined:

    As a CNCF hosted project, Vitess is part of a neutral cloud native foundation aligned with its technical interests, as well as the larger Linux Foundation, which provide the project with with project governance, marketing support and community outreach.

    For more on Vitess, read DZone:undefined:’:undefined:sLaunching Vitess: How to Run Youtube:undefined:’:undefined:s MySQL Sharding Engine, or watch the the recording of theVitess beyond YouTube session from Percona Live Open Source Database Conference 2017. You can also read Vitess:undefined:’:undefined:guide to getting started on Kubernetes.

    The postCNCF to Host Vitess appeared first onThe Linux Foundation.

    https://www.linuxfoundation.org/cloud-containers-virtualization/cncf-host-vitess/





  • Make ISO from DVD

    In this case I had an OS install disk which was required to be on a virtual node with no optical drive, so I needed to transfer an image to the server to create a VM

    Find out which device the DVD is:

    lsblk

    Output:

    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 464.8G 0 part ├─centos-root 253:0 0 50G 0 lvm / ├─centos-swap 253:1 0 11.8G 0 lvm [SWAP] └─centos-home 253:2 0 403G 0 lvm /home sdb 8:16 1 14.5G 0 disk /mnt sr0 11:0 1 4.1G 0 rom /run/media/rick/CCSA_X64FRE_EN-US_DV5

    Therefore /dev/sr0 is the location , or disk to be made into an ISO

    I prefer simplicity, and sometimes deal with the fallout after the fact, however Ive repeated this countless times with success.

    dd if=/dev/sr0 of=win10.iso

    Where if=Input file and of=output file

    I chill out and do something else while the image is being copied/created, and the final output:

    8555456+0 records in 8555456+0 records out 4380393472 bytes (4.4 GB) copied, 331.937 s, 13.2 MB/s

    Fin!

    read more
  • Recreate postrgresql database template encode to ASCII

    UPDATE pg_database SET datistemplate = FALSE WHERE datname = 'template1';

    Now we can drop it:

    DROP DATABASE template1;

    Create database from template0, with a new default encoding:

    CREATE DATABASE template1 WITH TEMPLATE = template0 ENCODING = 'UNICODE'; UPDATE pg_database SET datistemplate = TRUE WHERE datname = 'template1'; \c template1 VACUUM FREEZE;

    read more
});