Pharos Editions

[Margarita Lovvorn]

JarretMiddleton is the author of An Dantomine Eerly and the forthcoming novel, Darkansas. His fiction, essays, and reviews have appeared in print and online. He is the founding editor of Pharos Editions, a classics project that partners with contemporary authors to select and re-issue their favorite out-of-print books, now a new imprint of Counterpoint Press. More at www.pharoseditions.com and www.jarretmiddleton.com.

Ethan Nosowsky, McSweeney's editorial director since late 2011, will return to Graywolf Press on April 15 as editorial director there. Nosowsky was editor-at-large at the Minneapolis literary nonprofit press between 2007-2011.

Grand Central has delayed publication of Jane Goodall's Seeds of Hope: Wisdom and Wonder From the World of Plants after it was found that multiple passages in the book were borrowed without attribution from Web sites including Wikipedia.

In light of last week's news that Google has pulled the plug on print editions of Frommer's guidebooks, Amanda D'Acierno, senior v-p and publisher of Fodor's Travel, made a few comments about her company's commitment to print guidebooks.

On Friday, the Wall Street Journal provided an update on the standoff between Simon & Schuster and Barnes & Noble that has resulted in the chain cutting the number of titles it is carrying from the house and the amount of promotion support the books are getting.

Veteran Canadian publisher Scott McIntyre described the dismantling of D&M Publishers, the iconic Canadian independent publishing house he cofounded 40 years ago, as the result of an unfortunate confluence of circumstances.

Publishers prepare to pack for London, while the Supreme Court sends John Wiley & Sons packing with a copyright-related ruling that the First Sale doctrine applies as well in Bangkok as it does in Berkeley. Listen here.

Simon & Schuster is making available to authors information about infringement and unauthorized copies of their works that the publisher receives from Attributor, its service engaged to help fight piracy.

Ecco and Major League Baseball Advanced Media have created a new series of enhanced e-books for the Kindle, Nook, and iPad. Called MLB.com PLAY BALL Books, each enhanced e-book will feature 20 minutes of video, plus photos and interactive sections with stats and other elements.

Kubernetes is probably the hottest IT trend in 2019, as the popularity of conferences such as KubeCon indicates. K8s (as commonly stylized) not only realizes the elusive DevOps dream goal of reliably and quickly deploying applications from development to production thanks to the lightweight, immutable infrastructure properties of containers. It also allows process isolation at scale which in turn provides much-needed cost optimizations to ever growing applications, both in terms of storage and compute needs. Last, the portability of containers and Kubernetes across on-premises and cloud environments makes them an ideal choice for organizations that want to achieve true independence from infrastructure providers and spin up development, test or production environments wherever they see fit.

Be prepared to repeat at least steps #4 and #6 for any additional Helm package you must deploy and you may soon realize setting up a fully configured Kubernetes is not for the faint-hearted. It might still work for you if you only have one such cluster to set up but what if you have to deploy many Kubernetes clusters for developers and testers, all initially set up with the exact same configurations?

This is where the Pharos distribution comes to the rescue. The Kontena team has done a superb job at packaging the upstream distribution of Kubernetes with tons of useful add-ons such as an NGINX Ingress controller, a network load balancer (based on MetalLB), cert-manager and Kontena Lens, a dashboard masterpiece that radically simplifies the management of Kubernetes clusters through a powerful graphical user interface. You can virtually run any kubectl command in Kontena Lens, something you would be hard-pressed to achieve with the stock Kubernetes dashboard. Here is the main page you see once you sign in into Kontena Lens:

Kontena Lens includes many useful capabilities such as live inspection of log files inside each container in a pod, pod filtering by wildcard search on name and namespace, ability to execute shell commands inside pods, as well as the ability to visually view and edit every single Kubernetes component such as pods, deployments, jobs, services, ingresses, storage classes, PVs, PVCs and more. For instance, the following screenshot provides the full view of a GitLab gitaly pod, with a highlight on the gitaly container itself (there are 2 other containers in that pod, which are not shown below).

Suffice it to say that the initial deployment of a Pharos cluster with all the add-ons you require can be achieved in one single command line (after you have pulled your Pharos distribution using the chpharos tool):

One of the useful integrations available in Kontena Lens is the ability to add custom Helm chart repositories. The following screenshot shows v2.5.0 of the Pure Service Orchestrator available in a 2.3.8 Pharos cluster (in the Apps tab):

However, this Helm Charts repo integration only takes care of steps #3 and #4 above (deploying Tiller and adding custom Helm charts to a K8s cluster) and you would still have to manually deploy your Helm chart using your custom Helm values file, which is a must for Pure Service Orchestrator, since it requires environment-specific values. This can be achieved directly from the Lens UI by pressing the Install button for the selected Helm chart. You would then have to customize the default chart config file inside Kontena Lens and deploy your manually configured Pure Service Orchestrator instance in your cluster. The screenshot below highlights the manual process you would have to go through:

To generate the API token, you will need to SSH into your FlashBlade and uses the pureadmin create --api-token command (or the pureadmin list --api-token one) to create (or retrieve) the API token for the pureuser user.

While the Helm Charts repo integration available in Kontena Lens alleviates the need to add custom charts to a Kubernetes cluster deployed with Pharos, it is most appropriate for charts that must be manually deployed by developers or application owners, potentially long after the initial Kubernetes installation.

For system-level charts that set up core functionality such as persistent storage or metrics, Pharos provides another Helm add-on, available since the Pharos 2.3 release. The Helm add-on (not dependent on Kontena Lens and available in the OSS version of Pharos) allows the deployment of Helm charts, pre-configured with a customized values file. This can prove useful if you need to provision multiple Kubernetes clusters that will all use the exact same set of Pure Storage appliances. For instance, if you have a valid and properly configured pure-values-dev.yml file available, you can drop it in the same folder as your Pharos cluster-dev.yml definition file and add the helm add-on in the cluster-dev.yml file, as follows:

Note also that the helm add-on should be configured before the kontena-lens add-on in the Pharos cluster definition file, as is the case in my sample cluster-dev.yml file. This allows PSO to be installed before Kontena Lens and can therefore properly provision the Redis PVC with a pure storage class, as shown in the screenshot below:

Thanks for your participation during the Inspire Campaign focused on outreach to outside knowledge networks from February 2017. I'm interested in hearing your experience during the campaign, so if you're able, I invite you to complete this brief survey to describe how you contributed to the campaign and how you felt about participating. I want to improve how campaigns are run, so let me know if there's something that could be done better for next time.

Hi there, there was a error with the Inspire survey link that caused the survey to be shown as expired, but has now been fixed. The link in the above message should now bring you to the survey. Apologies, I JethroBT (WMF) 19:20, 31 March 2017 (UTC)Reply

We will be hosting a public event online to present the data, a few examples on how teams will be using it for annual planning, and what are next steps for this project. The event will take place on Tuesday, October 10, at 9:00 am PST (1600 UTC), and the presentation will be in English. You can watch the livestream here, and ask question via IRC on #wikimedia-office.

This is to introduce you to a new Wikimedia project called The AfroCine Project. This new project is dedicated to improving the coverage of the history, works, people, places, events, etc, that are associated with the cinema, theatre and arts of Africa, African countries, the Caribbean, and the diaspora. If you would love to be part of this (or you're already active in this area), by coordinating local programmes around African cinema (independently or otherwise) in your community or local Wikipedia, kindly list your username or organization as a participant on the meta project page here.

Furthermore, In the months of October and November, we are organizing a global contest and edit-a-thon tagged: The Months of African Cinema. If you would love to join this exciting event, also list your username as a participant on the English Wikipedia page. If you would love to lead this contest (or any other relevant program) for a non-English Wikipedia community, please feel free to translate the English Wikiproject page to your local language Wikipedia, or you can create one from scratch!

This is a global online edit-a-thon, which is happening in at least 5 language editions of Wikipedia (en, he, es, it, bn) and Wikidata. Join us in this exciting venture, by helping to create or expand articles which are connected to this scope.

If you'd love to organize this contest for your local wiki or organize in-person events centred around this project, or you need further information about the AfroCine Project, please leave a message on the project talkpage. See you around :).--Jamie Tubers (talk) 22:50, 03 October 2018 (UTC)Reply

3a8082e126