Gauge Instruments makes minimal analog watches inspired by precision instruments and vehicles. Their Classic Black and Classic White are prime examples of their approach. The watches have 42mm metal cases, a butterfly buckle and an anti-reflective sapphire crystal.
Graph databases are designed for applications that need to quickly make sense of the associations between different groups of data. They allow users to store related bits of data as a graph that can be accessed in a single operation, rather than a bunch of individual queries for all that data.
Companies building social networks, fraud-detection apps or personalization features for existing apps, for example, can take advantage of graph databases to deliver more flexibility and speed. AWS rival Microsoft’s Azure Cosmos DB also offers graph database capabilities.
Amazon Neptune will replicate six copies of your data across three availability zones within AWS computing regions, and AWS said it was designed for 99.99 percent uptime. It is available in the US East (Northern Virginia), US East (Ohio), US West (Oregon), and EU (Ireland) regions, with more expected to arrive later this year.
Oracle Cloud Infrastructure (OCI) is Oracle’s second-generation cloud infrastructure. These new datacenters were built with the latest high-performance servers (Oracle’s X7 Servers) and were designed to eliminate network and CPU oversubscription. Due to high-performance systems and the multiple availability domains (ADs) in each region, these are the preferred environments for deploying MySQL. Since MySQL deploys on Compute services (IaaS), look for “Oracle Cloud Infrastructure Compute” (not Classic) on this region map.
Beyond the benefits of the second-generation datacenters, why deploy MySQL on Oracle’s cloud? Here’s a few of reasons people are choosing MySQL on OCI:
No vendor lock-in: pay minimal or no egress charges and directly access your binary data files. Getting your data out of other clouds can be tedious and expensive.
Consistency: use the same database on-premise as on-cloud. It’s the MySQL Enterprise Edition, the same version available from the website. Use the same monitor for both on-premise and cloud.
Support: rely on database support from the team that develops MySQL
As a new platform, extra steps are required to install the MySQL Cloud Service. Otherwise, the install will default to OCI-Classic and you’ll miss the benefits of the second-generation datacenters.
Sign in to your Cloud Account (cloud.oracle.com) and go to My Services Dashboard. Click the Navigation menu icon navigation menu in the top left corner of the My Services Dashboard and then click Compute.
This will bring you to the OCI, Oracle Cloud Infrastructure, console.
CREATE A COMPARTMENT
Create a compartment called “demo”.
Click Identity. From left menu, choose Compartments and Create Compartment
Name your compartment “Demo”.
2. CREATE A NETWORK
Then, create a virtual cloud network with three public subnets, which will span 3 Availability Domains (AD). Although it includes a built-in firewall to prevent intrusion, a more secure network should be used for production systems ( see VCNs and Subnets ).
Click Networking, Virtual Cloud Networks
Click Create Virtual Cloud Network
Complete the following fields:
Create In Compartment: Demo
IMPORTANT: Select option: Create Virtual Cloud Network plus related resources
Click Create Virtual Cloud Network
3. ENABLE PLATFORM AS A SERVICE (PaaS) ACCESS
This next step enables the MySQL Cloud Service to access the underlying compute and storage resources.
From left menu, select the dropdown for compartment list and select your root compartment.
From top menu, click Identity, Policies and Create Policy.
Name: I chose “MySQLPaaS access”
Add four Policy Statements exactly like the following:
[ note: if you chose a different compartment name than demo, substitute accordingly in the following statements]
Allow service PSM to inspect vcns in compartment demo
Allow service PSM to use subnets in compartment demo
Allow service PSM to use vnics in compartment demo
Allow service PSM to manage security-lists in compartment demo
4. CREATE A BUCKET FOR OBJECT STORAGE
Click Storage, Object Storage
Switch compartment (bottom left menu) to “Demo”
Chose Create Bucket
Next, create a swift password to authenticate to the object storage. This will be required when setting up MySQL.
Click Identity, Users
For your user, choose the elipses on right and select View User Details
On left menu, choose “Auth Tokens”
Generate Token Important: Write down this token. It’s unavailable after it’s created.
While your here, write down the user name for which you’ve created this token. It should be something like: firstname.lastname@example.org. You’ll need this later.
If you have issues, the above steps are well-documented here.
Before continuing to the next step, please write down the following from the current OCI console. You’ll need this info for the next steps.
User name: Choose Identity, Users. This should be the user for whom you generated the Authentication Token in the previous step.
Tenancy and region: Noted at top of screen
Bucketname. Choose Storage, Object Storage. Note the name of the bucket that you created
5. DEPLOY THE MYSQL CLOUD SERVICE
First, navigate from OCI (Oracle Cloud Infrastructure) to the MyServices console. On the very top menu, click My Services. This should bring you back to the MyServices Dashboard.
To view the MySQL Cloud Service, either click Customer Dashboard” or click the navigation menu ( three parallel lines) in upper left corner.
Click MySQL and choose Open Service Console and then Create Instance.
The following screenshots show appropriate field entries. Once you select “Region”, additional fields will display:
Availability Domain: Select AD1
Subnet: This was setup in step #2.
Click Next and complete Service Details.
A full explanation of fields are available in the online documentation. However, Backup and Recovery Configuration requires further explanation.
Cloud Storage Container: The OCI format is https://swiftobjectstorage.<region>.oraclecloud.com/v1/<namespace>/<container>
For me, the region is us-ashburn-1, but this may vary depending on your location and your account. The namespace is the tenancy and it’s the name of your oracle account (hint: it’s in your current URL: https://psm-<tenancy>.console.oraclecloud.com). We named our container MySQLBackups. In my case, the URL is https://swiftobjectstorage.us-ashburn-1.oraclecloud.com/v1/015010/MySQLBackups. You will need to change the tenancy (015010) and possibly the AD (us-ashburn-1).
Username: This is the user for which we created a token when setting up OCI. It’s not the name for which you sign into your MyService Dashboard.
Password: This is the authentication token created in Step #4.
Click Next and Create. After a few minutes, your MySQL instance will be running. This process has deployed MySQL onto an Oracle Compute instance (similar to EC2 instance) on the next generation datacenter. Once it’s created, identify the public IP address and ssh into the instance. Use ssh opc@xxxxxx to log into the instance. From here, you have full control of your instance.
Of course, that’s a lot of steps to create a MySQL Cloud Service. Further automation is in development. In future blogs, I’ll include terraform automation instructions. Additionally, with multiple AD’s, we can set up replication for high availability.
If you’ve seen our excellent series on different species of wood, by looking at boards you can identify the ones most commonly used in furniture and homebuilding. But do you know what an actual Poplar, Walnut or Zebrawood tree looks like? Could you actually draw one if you were playing some forestry version of Pictionary?
Solo: A Star Wars Story offers a shadier look into the period between Revenge of the Sith and A New Hope, removed from stories of the Rebellion vs. the Empire, and Jedi vs. Sith… mostly. But if you’ve only kept up with the Star Wars movies, and not the entirety of the multimedia behemoth that the franchise has become, one of Solo’s greatest surprises is likely also its most baffling. If you were confused, then here’s what you need to know.
Late into the events of Solo, Bantha poodoo has hit the fan in the most spectacular of manners for Han and his friends. Their attempt to deceive criminal overlord Dryden Vos out of the deal they’d cut with him goes sideways when Han’s would-be mentor Beckett double-crosses the group, and Dryden himself is killed in a scrap with Qi’ra and Han. As Han chases after Beckett, Qi’ra, although now seemingly free of the grip the Crimson Dawn crime syndicate has on her, chooses to return to the fold rather than running off with Han. She opens a communication channel to the Dawn’s high command—revealing the syndicate is run by a very familiar face:
Darth Maul himself. Yes, if you’ve only kept up with the movies, Maul was last seen getting lopped in half by a young Obi-Wan Kenobi during the climax of The Phantom Menace, seemingly plummeting to his death on Naboo. But Maul survived that not-so-fatal blow, and has actually been around for quite a while again in Star Wars canon, even before Disney purchased Lucasfilm. In fact, to know more about how Maul got from The Phantom Menace to Solo (and from half a Zabrak to a whole person again, more or less), we need to head into the world of Star Wars animation.
The Return of Maul
Maul’s re-emergence into Star Wars canon begins in the Clone Wars TV series’ fourth season, which introduced Maul’s brother, the exquisitely named Savage Opress. Savage and Maul (and their other brother, who I kid you not, is named Feral) grew up on the planet Dathomir, home to the fabled, witchy Force users known as the Nightsisters. While Maul was plucked from the world by Darth Sidious to become his apprentice, Savage was left behind—until the Clone Wars, when the dark assassin Asaaj Ventress (a former Nightsister herself) headed there after being betrayed by Count Dooku.
Ventress chose Savage as her apprentice in a quest for revenge against Dooku, but after even more betrayals—lots of betrayal among Dark Side users, as you’d expect—Savage struck out on his own, operating on information given to him by the leader of the Nightsisters, Mother Talzin, that Maul had survived his battle on Naboo and was living on the junkyard world of Lotho Minor.
That indeed proved to be the case—surviving his duel with Obi-Wan by feasting on the Dark Side energies of his own rage (at being chopped in half!), Maul managed to save his upper body from destruction and drag himself to a trash container, which was then dumped on Lotho Minor. In the years between his “death” on Naboo and Savage finding him—during which he cobbled himself a set of spider-y mechanical lower limbs—Maul’s mind was fractured, not just by his defeat but by Sidious’ abandonment of him. All that was left was a singular, all-encompassing thirst for vengeance against the Jedi and Obi-Wan, which Savage and Talzin were all too willing to stoke.
After bringing him back to Dathomir and using Nightsister magic to restore his mind (and replace Maul’s spidery-y legs with more humanoid ones), Savage found himself apprenticed to Maul in a quest to destroy Obi-Wan, one that eventually culminated in a duel between Maul, his hated enemy, and the Jedi Knight Adi Gallia. Gallia fell in battle, but Obi-Wan turned the tide on the Zabrak brothers, leading to their retreat. Maul immediately hatched more plans to get at Kenobi.
The Lord of Mandalore
Maul and Savage went big for their next grab at power, allying themselves with the Mandalorian Death Watch group’s Pre Vizla in their bid to overthrow the peaceful diplomatic rule of Mandalore’s current ruler, Satine Kryze (who was also once a potential paramour for Obi-Wan, before he had to distance his attachment to her). Using an army of Black Sun gangsters to bolster the Death Watch’s forces, the trio formed the Shadow Collective, and staged a coup attempt on Mandalore—but Vizla betrayed Maul (gasp!), trying to take rule of the planet for himself, leading to a duel between the two that culminated with Maul taking Vizla’s weapon, the legendary Mandalorian Darksaber, and beheading the Death Watch leader, taking his place as the current ruler of Mandalore.
Using Satine as a hostage to draw Obi-Wan out alone, Maul enacted a fraction of his vengeance against the Jedi by killing Satine in front of him—but his victory over Obi-Wan was short-lived. The Death Watch forces that refused to pledge loyalty to him after Vizla’s death freed Obi-Wan from prison, but worse, Maul’s re-emergence on such a major stage attracted the attention of a far bigger threat: his former master, Darth Sidious.
Sidious came to Mandalore to ensure that the Sith’s rule of two—currently taking the form of Sidious and Dooku—stayed true, dueling both Maul and Savage and ultimately killing the latter. Maul was kept alive by Sidious, however, who planned to use him to draw out Talzin, so he could eliminate the last of any meddlesome threats standing in the way of his imminent ascendance to rule over the entire galaxy.
The Rise of the Empire and Solo
Although Clone Wars came to an end before Sidious’ plans for Maul could be shown on screen, the gaps were filled in by both the Darth Maul: Son of Dathomir comic (one of the last Star Wars comics published by Dark Horse before Disney’s purchase of Lucasfilm lead to the rights transferring over to Marvel, and adapted from a scrapped Clone Wars storyline) and the Ahsoka novel. The former sees Sidious successfully eradicate Talzin and the Nightsisters, leading to Maul fleeing once again back to his stronghold on Mandalore—only for the latter to see Ahsoka Tano joining Republic forces in the final days of the Clone Wars to help liberate the planet from Maul and his Shadow Collective, although Maul escaped.
It is after these two stories that Maul’s Solo appearance lies. Solo is largely set in the earlier half of the 20-year gap between Revenge of the Sith and A New Hope, making Maul’s move back into the world of organized crime in the Crimson Dawn (itself based on Dathomir, according to his call with Qi’ra in the movie, so Maul is back on his homeworld) an unsurprising leap, given his history of working with gangsters and criminals during the formation of the Shadow Collective. Although we don’t know for sure, perhaps the Dawn is made up of what was left of Maul’s loyal forces from the Collective, which would explain why Maul is its overarching leader. Now that Maul has returned to the cinematic portion of the Star Wars universe, it’s likely that these gaps will be filled in through comics and books, giving us the exact details of how the Dawn and Maul rose to prominence in the galactic underworld.
But Maul’s story doesn’t end with Solo. However, we’ve already seen its end, which happens years after the event of the movie, in the recently-concluded Star Wars Rebels TV series.
The Final End of Darth Maul
Maul returned to TV screens during the climax of Rebels’ second season, set just a handful of years before the events of A New Hope. Fledgling Jedi-in-training Ezra Bridger encountered him on the planet Malachor, as the former Sith searched for Dark Side artifacts he could use to bring down Sidious and his Empire. It was suggested he’d been there for some time, implying that either Maul had left the Crimson Dawn in the intervening years or that the crime syndicate had become severely diminished.
Maul being Maul, he betrayed Ezra and fled Malachor, only to capture Ezra and his Rebel friends several months later in an attempt to gain access to an old Jedi Holocron saved by Ezra’s master, Kanan. Combining the Holocron with a Sith one he recovered on Malachor, Maul is granted a vision that confirms that his hated foe Obi-Wan is alive and hiding on a planet with twin suns, leading to a final conflict that, for Maul, had been decades in the making.
After locating Obi-Wan on Tatooine, however, Maul’s quest for vengeance came to an unexpected end… for him. After Maul had figured out his exile on the desert world was not to avoid the eye of the Empire, but to protect someone capable of bringing it down, the aged Jedi cut down Maul for good. Although unsuccessful in his own quest to kill Obi-Wan, Maul’s dying words were to ask if Kenobi’s charge was the fated chosen one. Kenobi replied in the affirmative and Maul died knowing at least someone would get the vengeance against Darth Sidious that he had so desperately craved.
Although we’ve seen a great deal, Solo proves there is still so much about the life and times of Maul—previously nothing more than a cool-looking henchman who appeared in a single movie—left to explore. A lot of the gaps have already been filled in thanks to Clone Wars and Rebels, but his surprising return in the latest Star Wars film means there’s still a lot more we have to learn about the former Dark Lord of the Sith.
We manage several hundreds of MySQL servers, We carefully benchmark and build custom database infrastructure operations for performance, scalability, availability and reliability … But What if we have provision for auto sizing of MySQL system variables innodb_buffer_pool_size, innodb_log_file_sizeand innodb_flush_method ? Actually, These are top 3 system variables we consider tuning for MySQL performance and when we first read about this feature, we got super excited so did some research and decided to write this post:
What was our first reaction, when we first read about innodb_dedicated_server ?
Wow, That will be awesome … Indeed, When we manage several hundreds of MySQL instances, This feature will really improve efficiency and DBA Ops. governance.
Now, Let us explain what we have found:
How does innodb_dedicated_server system variable in MySQL 8.0 size the following variables:
<1G – 128M (default value if innodb_dedicated_server is disabled / OFF)
<=4G = Detected Physical RAM * 0.5
>4G : Detected Physical RAM *0.75
<1G: 48M(default value if innodb_dedicated_server is OFF)
Set to O_DIRECT_NO_FSYNC if the setting is available on the system. If not, set it to the default InnoDB flush method
The first impression of innodb_dedicated_server system variable in MySQL 8.0 is impressive, Definitely will deliver much better performance than default value. This new feature will configure the MySQL system variable mentioned above more intuitively to improve DBA productivity. Till MySQL 5.7 it was always presumed 512M RAM with the default settings.
Are we going to follow this in our daily DBA checklists ?
Not really, We are an very conservative team about implementing the new features immediately in the critical database infrastructure of our customers, Also we are afraid about the isolated issues due to auto sizing of MySQL / InnoDB memory structures, Let’s explain why we will not be using this feature immediately for our MySQL 8.0 customers:
We carefully size InnoDB memory parameters on various factors like database size, transaction complexity, archiving policies etc. So we want to be hands-on or follow manual sizing of system variables innodb_buffer_pool_size, innodb_log_file_size and innodb_flush_method.
Capacity planning and sizing – We are always afraid of over / undersizing of our database infrastructure operations. Database infrastructure operations reliability is very critical for us, We have dedicated team with-in to monitor and trend database infrastructure operations and system resource usage consumption.
P.S – innodb_dedicated_server system variable is a relatively new feature, We are confident MySQL engineering team will be improving this component in coming days so our perspective will also change, We will never forget then to blog about this feature and why we are seriously thinking about implementing it for our customer production infrastructure.. Technology keeps changing for good, We are adaptive for the change !
It wasn’t the most authentic of settings, but my maiden voyage to the land of Mexican elotes took place via a Chicago White Sox game. Two thoughts stuck: “These greedy bastards are charging $6 for a small tray of corn?!” More consequentially: “Boy, sweet corn with mayo + butter + cheese + lime + chili is mighty delicious.”
Like baseball, fireflies, and small-town parades, elotes are a harbinger of summer, a simple but impressive and indulgent showcase for sweet corn. It’s an all-dressed-up version of corn-on-the-cob, where a helpful slather of mayonnaise and butter helps cheese and chili powder adhere to the kernels. The overpriced ballpark elotes left such an impression, the next day I sought out a more genuine version in Chicago.
I found it in the city’s Little Village neighborhood, the residential and economic heart of Chicago’s Mexican populace. In a city where regulation and red tape all but suppresses street food culture, the only carts I encountered were for elotes and tamales. At several of these elotes stands, the ritual was the same: The vendor would remove a corn-on-the-cob from a steaming cooler. Holding the cob upright by its stick, she would slice vertically, the kernels landing onto a plastic mat. She would fold the plastic mat in half and dump its contents into a styrofoam cup. The vendor would then juice a lime over the corn, scrape off a spatula’s worth of mayonnaise against the cup, squeeze on imitation butter, and spoon the feta-like cotija cheese and chili powder on top. This set me back $2.50, though the norm is to hand over three singles and tell her to keep it. (Purists will argue elotes is served on-the-cob, while esquites is off-the-cob and pan-fried. But elotes has become the catch-all word for the dish, and the term we’ll use here.)
Whether served on the cob or off, this marriage of sweet, fat, spice, citrus, and salty cheese is dangerous and enticing, a combination sounding more like a misprint than carefully considered. The undisputed best way to enjoy sweet corn is grilled with a pat of butter, so elotes might be seen as a next-level application, a justified gilding of the lily.
As with all dishes, but especially with elotes, achieving balance is key. While you could easily cut corn and fold in the mayonnaise, cheese, and spices (and making it easier to eat), there’s just something tactilely and visually satisfying about serving elotes on the cob (plus, it discourages you from adding too much mayonnaise, as a light slather on the cob suffices). The recipe below comes via chef Andres Padilla of Chicago’s Topolobampo, founded by Rick Bayless and recently awarded outstanding restaurant, the top prize of the James Beard Foundation.
In this recipe, Mexican crema (or sour cream) is employed, though you can substitute the more common mayonnaise. Boiled corn will also do, but please consider taking the extra step and grill whole cobs over charcoal. It doesn’t even compare.
Elote asado (charcoal-grilled corn with cream, cheese and chile)
1/2 cup thick cream or commercial sour cream mixed with a little milk or cream
1/3 cup crumbled Mexican queso anejo or queso fresco, or cheese like Parmesan, feta, cotija, or farmer’s cheese
1 Tbsp. hot powdered chile (ground chile de arbol, guajillo, or New Mexico chile)
1. About an hour before serving, place the ears of corn in a deep bowl, cover with cold water and weight with a plate to keep them submerged. Light your charcoal fire and let it burn until the bed of coals is medium-hot; adjust the grill four inches above the fire.
2. Lay the corn on the grill and roast for 15 to 20 minutes, turning frequently, until the outer leaves are blackened. Remove, let cool several minutes, then remove the husks and silk. About 10 minutes before serving, brush the corn with melted butter, return to the grill and turn frequently until nicely browned. Serve right away, passing the cream, cheese, and powdered chile for your guests to use to their own liking. Serve with a wedge of lime.
Bonus variation: Esquites (as served in Toluca and Mexico City)
Cut the kernels from six cobs, then fry in three tablespoons lard, vegetable oil, or butter, with hot green chile to taste (seeded and sliced) and two or three tablespoons chopped epazote. Season with salt.
Getting rid of weeds is a pain. Pluck them, and they come back. Kill them with chemicals, and the ground is poisoned for other plants. These organic corn farmers demonstrate a much more reliable, chemical-free, and downright spectacular method to clear the ground – FIRE!
The latest Ebola outbreak has claimed yet another life in the Democratic Republic of Congo, raising the death toll to 12—though the actual number may be as high as 27. Using a strategy known as “ring vaccinations,” officials began treating doctors and other frontline healthcare workers in Bikoro, the town where the outbreak was first declared in early May.
As of today, the DRC says there are about 56 cases of hemorrhagic fever (a primary symptom of the disease) and 35 confirmed Ebola cases, of which 13 are probable and eight suspected. This is the third Ebola outbreak in the DRC in the past five years and the ninth since 1976 when the disease was first identified. The Democratic Republic of Congo is located in the heart of sub-Saharan Africa and is home to nearly 79 million people.
Earlier today, DRC Health Minister Oly Ilunga traveled to Bikoro, a small market town located 78 miles (126 km) south of Mbandaka, to oversee the vaccinations of at least 10 people. It was here that the outbreak was first declared three weeks ago and at least five Ebola deaths have occurred so far, according to the Associated Press. Officials are employing a strategy known as ring vaccinations in which the people who are most likely to be infected are treated. Today’s vaccinations included three doctors at Bikoro Hospital, two health experts, two nurses, a woman’s community representative, and a pygmy representative. The drug used was the experimental rVSV-ZEBOV, and all vaccinations were voluntary.
Ring vaccinations started on May 21 in Mbandaka, with 7,560 doses ready for immediate use, according to the World Health Organization. The drugs were donated by its developer, Merck, while Gavi, the Vaccine Alliance has contributed $1 million towards operational costs. Ground teams are currently searching for and following up with all known contacts, of which 600 have been identified to date.
“Implementing the Ebola ring vaccination is a complex procedure,” said Matshidiso Moeti, WHO Regional Director for Africa, in a statement “The vaccines need to be stored at a temperature of minus 60 to minus 80 degrees centigrade and so transporting them to and storing them in affected areas is a major challenge.”
On May 18, WHO said the current outbreak is not yet an international emergency, but admitted a “vigorous” response was still necessary, both on the ground and in terms of funding its $56.8 million Ebola strategic response plan. WHO is currently working to prevent the disease from crossing the DRC’s nine borders, CBS reports. Also, several schools have been shut down in the Iboko health zone as a precaution. The next few days and weeks are critical in ensuring the outbreak doesn’t escalate any further.
The current outbreak involves the Zaire Ebola virus, which is known to be fatal in up to 60 to 90 percent of cases. Ebola spreads from person to person via contact with bodily fluids, but it often makes the jump to humans from wild animals such as bats and monkeys.
CEO: I can’t take you seriously because there’s a typo in your slide deck. You’ve lost all credibility because of your sloppy presentation. And don’t mention my wife in your slide deck. Dilbert: That’s “wi-fi.”