text:
Cloud Native Transformation and Multi Cluster Management
1 Introduction 2 Background 3 Multi Cluster Use Cases 4 Cloud Native Deployment / Multi Cluster Management 5 Kubernetes Governance & Cloud Native Migration Challenges 6 Cloudify Kubernetes Multi-Cluster Use Cases 7 Takeaways 8 Why Cloudify 9 Glossary
The growth of adoption for cloud computing has been growing at a fast clip, and public cloud infrastructure (IaaS) spending has crossed the $150B threshold. On this infrastructure run the familiar cloud platforms, dominated by Amazon AWS and Microsoft Azure. On the application front, the cloud native movement has been rising, and adding a layer of abstraction on top of the virtual machines and hardware traditionally dispensed by the cloud providers. The cloud native platform of choice is Kubernetes, including the major cloud providers that provide Kubernetes clusters on demand (e.g. AKS, EKS, GKE). In addition to these developments, the use of multiple cloud platforms has grown to be commonplace in the industry. This article discusses the foundational technologies behind cloud computing, containers, Kubernetes, cloud native meaning, and the challenges related to delivering and operating applications in a multi-cloud, multi-Kubernetes-cluster environment.
The journey to cloud computing came with the advent of the virtual machine (VM). VMs are essentially computer hardware emulated in software. The concept of a virtual machine is almost as old as computing, and early versions of it began appearing in the 1960s. The compute power of the time was limited, and VMs were really only practical on mainframe and minicomputers. As the compute and memory capacity of computers grew over the years, especially microcomputers, the capacity growth greatly outpaced the needs of typical software applications and VMs became practical. A single machine could masquerade as multiple machines, and maximize its utilization (cost efficiency). Because they emulate hardware, and are supported by chipsets, virtual machines provide excellent isolation when sharing a compute host.
If VMs emulate machines, containers just slice one up. "Container" is a name for a collection of technologies that can provide isolation for ordinary processes. An early form of this technology was provided by the chroot system call, which set the effective file system root for a process and its children. This provided a 'jail', limiting the damage the process could do if it had access to the real '/' filesystem. Containers use many modern operating system kernel features to provide sophisticated file systems, isolation (various kinds of namespaces), and resource consumption limits (cgroups). A container is an environment for running ordinary processes on a compute host (including VMs), and generally has access to shared system libraries and sensitive areas on the host filesystem. As such, they are less secure than VMs.
The term "cloud native" entered the mainstream with the founding of the Cloud Native Computing Foundation (CNCF) in 2015. It refers to a technological and cultural shift in the way applications are designed, deployed and managed, with the dynamism of cloud computing as an inspiration. What is a cloud native application? A cloud native application takes a service oriented approach, where applications are composed from independently operated services (microservices), and scalability and high availability are fundamental features. The idea (and tradeoffs) behind microservices is very similar to Service Oriented Architecture which was bound up with the web services craze of bygone years. The benefit is decoupling, and the costs are performance and complexity.
The granularity of a cloud native application is not a one size fits all proposition. Service decomposition directly serves the needs of agile teams to deliver frequently with minimum disruption. Updating a single service in a cloud native app is the equivalent of changing a tire on a running car. An adopter of cloud native principles can expect higher service availability and agility, as services can be added, removed, and repaired on demand. Microservices also offer more flexibility when it comes to fault tolerance and scaling as well. But these advantages come with a cost in terms of complexity and performance, and must be considered carefully on a case by case basis. For a deeper dive into cloud native concepts, see one of the definitive posts by Martin Fowler.
Kubernetes is a platform for managing cloud native applications. Kubernetes is written in Go and was open-sourced in 2014 by Google. Since then it has become one of the most popular open source projects on the internet, and really has no significant competition. Kubernetes is organized in hub/spoke architecture, using a control loop operational model. Work is done by multiple worker compute hosts at the behest of controllers running on the master. Managed entities (like containers) are described in manifests which are submitted to the master node, which triggers controllers that asynchronously fulfill the requirements of the manifest.
To address the popularity of Kubernetes, and the complexities of Kubernetes cluster management, several companies offer hosted Kubernetes as a service, such as Amazon EKS, Google GKE, Azure AKS, Redhat ROSA, and others. Kubernetes, which includes a cloud controller manager, is now positioned as a cloud neutral platform for application on public (and private) clouds, as well as edge computing environments. Applications can be written for Kubernetes (cloud native) and the portability aspects are delegated to the infrastructure layer.
The recent growth of multi-cloud computing solutions and the emergence of edge computing extend to the cloud native approach as well. In this approach, workloads can be allocated to different clusters, much as a multi-cloud deployment can target multiple clouds. A benefit of the cloud native approach targeting Kubernetes, is that the cloud differences can be dealt with at the platform level. This is particularly attractive when edge computing is involved. Since Kubernetes is just as happy running without a hypervisor (bare metal) as running in the cloud, the same platform can be scaled from lightweight edge, to massive VMs in the cloud without special provisions in the application stack. This is precisely the value proposition of VMWare Tanzu, which layers a standard Kubernetes distribution on top of ESXi.
Multi Cluster Use Cases
It's important to understand that there isn't a direct relationship between the number of clusters needed and the number of applications hosted. On Kubernetes, multiple applications can be deployed into isolated namespaces, providing the application with a kind of "virtual private cluster" experience. In other words, in the case of Kubernetes multi-cluster management, the need for workload isolation doesn't necessarily require adding clusters. The need for multiple clusters can be grouped into a few categories.
Software Delivery
Any company delivering services on Kubernetes will by necessity have multiple Kubernetes clusters. Advanced configurations will have automation to assist in software delivery across clusters designated for development, testing, potentially UAT, and production. Production itself may employ multiple clusters to enable canary rollouts and other reversible deployment schemes. The ability to automate the software delivery process is essential for establishing a repeatable, high quality process and delivering maximum value to customers as quickly as possible. An approach growing in popularity is Gitops, which integrates delivery with source code release processes. Multi Cluster configurations can be managed and versioned centrally in git, and utilized to produce repeatable deployments.
Operationally, this is perhaps the most obvious application for multiple clusters. Kubernetes workloads, properly deployed, are highly available by their nature, because of the closed loop approach Kubernetes takes to workload management. The "high availability" referred to here, is the availability of entire clusters. The ability to place clusters in different "availability zones", or fault independent locations. Doing so naturally requires a highly available means of load balancing traffic across the clusters as well as assessing their health on an ongoing basis.
SaaS Implementations
Software as a Service (Saas) companies that expand beyond a small scale require flexibility of workload placement based on security, regulations, and performance. The ability to easily migrate or establish new operations between the major Kubernetes cloud providers, and/or datacenters is a must to respond to market demands. Other considerations are high availability and dynamic scaling which are covered elsewhere on this list.
Workload Segmentation/Scaling
This category encompasses platform awareness/sensitivity and location sensitivity. Examples include:
Edge computing, 5G, CPE (and others) that need workload proximity to service consumers generally based on latency requirements. Besides latency, the need for service continuity at the edge, regardless of the health of upstream services.
The ability to scale workloads beyond a specific infrastructure provider.
Provider feature sensitivity for workloads better suited to specific providers (e.g. security features).
Cloud Native Deployment / Multi Cluster Management
The ability to deploy Kubernetes clusters naturally precedes any concerns over workload orchestration and cluster or multi-cluster management. A few years ago, the provisioning of Kubernetes clusters was complex and less well defined than now. Besides better support by orchestration tools for in-house managed clusters, all major clouds have added Kubernetes clusters on demand (as a service) making provisioning trivial.
Do It Yourself Provisioning
The highest effort approach to cluster provisioning is the do it yourself method. Only you can determine whether the benefits of self-provisioning and management are worth it. The benefits can be significant, including security, total control, and potentially performance. Bare metal hosting can provide surprisingly potent performance benefits. A Stratoscale study found that bare metal workloads can benefit by 25%-30% over hypervisor hosted workloads.
Most IT teams are more comfortable with the management of virtual machines however, and gladly trade the flexibility VMs provide over bare metal. In any case, when provisioning your own clusters, you will likely need tooling to deploy your clusters. Mainstream Kubernetes distributions like OpenShift have their own installation tools. Other companies like Rancher provide infrastructure independent solutions for performing Kubernetes multi-cluster deployment at scale. The scale of such solutions on premises deployments is of course capped by the size of your physical infrastructure. Multi-cloud deployment on cloud infrastructure is also available, providing a combination of control and scalability, at the cost of operational complexity.
Kubernetes As A Service
One step beyond self provisioning of cloud-based clusters is the use of Kubernetes as a cloud service. All major cloud providers provide SaaS oriented deployment and management of Kubernetes clusters on their cloud infrastructure, including Amazon AWS (EKS), Google Cloud (GKE), Microsoft Azure (AKS), IBM Cloud Kubernetes Service, and others. Managed Kubernetes services promise to offload the burden of deploying and managing clusters so resources can focus on higher value added layers (applications/services).
Multi-Cluster Management
Kubernetes multi-cluster management can be a complex beast to manage, especially at scale. And any organization using Kubernetes will likely need to manage multiple Kubernetes clusters, possibly including development, testing, staging, and multiple production clusters. The usual tasks frequently associated with operating system deployments are needed, such as location-aware installation, upgrades, patching, and security configuration. Besides the clusters themselves, the cloud native applications need to be deployed and managed, made more complicated when deploying on multiple clusters. Like most highly complex systems, a layer of automation is required to orchestrate complex workloads in a way that avoids chaos, as well as manage day to day operations.
Management Challenges:
Controlling ingress and egress network policies, both inter-cluster (if needed) and per cluster. Managing role based authentication. The coordination and updating of security configurations is one of the primary challenges of managing multiple clusters (or managing any complex system). A standardized, policy based approach is the primary tool for managing the potential combinatorial explosion of systems x users x roles x permissions.
This can be handled by the Kubernetes cluster autoscaler in many cases on a per cluster basis, assuming a supported cloud based hosting environment. The need to autoscale clusters on bare metal is a possible but less common requirement and requires sophisticated external orchestration. Responsive Kubernetes multi-cluster management opens the possibility of adding entire new cluster instances based on demand or rules/policies, along with decommissioning based on load or other criteria.
Workload Placement
Cluster selection by workload requirements, which might include latency, CPU requirements, physical location, or other functional and business considerations. This is a common requirement in edge scenarios, but can arise in many other common situations including selecting the cluster with the lowest current load. A key enabler of dynamic workload placement is the ability to deal with clusters as abstractions for workloads. This enables workloads to be fungible between different Kubernetes clusters, and so lets an orchestrator bind to individual clusters at deploy time. For example, a single workload can be deployed to multiple clusters in a single operation, or moved between clusters when conditions dictate.
The coordination of intercluster networking as the result of cluster deployments or scaling and migration activities. This could involve configurations of ingress and egress, or the construction and management of NFV networks to facilitate communication between workloads. An example is provisioning the connection between edge workloads and centralized management/visibility. This doesn't apply only to green field, pure Kubernetes applications, but also more common hybrid applications. In such applications networking between containerized workloads in Kubernetes and legacy systems must be configured in a secure and standardized way.
Troubleshooting/ Remediation
High level visibility into overall multi-cluster health, with the ability to drill down, discover causes, and effect remediation. Kuberentes' closed loop approach to resource management has within it an effective approach to handling and recovering from many routine operational problems (i.e. auto-healing). However, error recovery is only as competent as the workload support for it, and still requires oversight. The adding of multiple clusters only increases this requirement. Root cause analysis on a widely distributed system is very challenging, especially ones with ephemeral services and based on asynchronous message passing. There is no magic bullet for this problem, but tools like service meshes and log analysis can help.
An emerging class of multi-cluster management tools is addressing the needs arising from the need to manage multiple clusters. These tools attempt to provide visibility and control of clusters and the cloud native applications that run on them. These tools can be categorized into classes; tools provided by cloud vendors to manage "cluster as a service" instances that they offer, and tools that aren't limited to a single vendor. Some examples:
Amazon's Elastic Kubernetes Service provides a management dashboard that presents a list of configured clusters that you can drill down into. From this top level pane, you can also create and destroy clusters. Upon drilling down you are presented with a Kubernetes Dashboard that includes cluster overview metrics, including cpu, memory, and storage consumption, along with workload statistics. From here you can drill further down into individual cluster nodes. All clusters are created on AWS using the EKS service.
Google GKE
Google GKE, like EKS, presents a list of clusters from where you can drill into the details. GKE provides multi-cluster Kubernetes management via its MCS offering. From the top level you can add, modify, upgrade, and delete clusters. When drilling down, you are presented with a Google Kubernetes dashboard from where you can see and manage workloads, services, configuration, and storage.
MCS extends the Kubernetes service concept so it can span multiple clusters, providing a native way to describe multi-cluster services. To support access to multi-cluster services, it also provides a multi-cluster ingress. Cluster health and workload monitoring is provided by integrated dashboards. Like EKS, the management service (MCS) applies to GKE clusters only.
Azure AKS
Microsoft Azure's entry into the Kubernetes arena is called Azure Kubernetes Service, and provides features very similar to the other big providers. For multi-cluster management, Azure offers Arc, which provides multi-cluster Kubernetes management beyond the Azure cloud. A prerequisite for this capability is the use of Azure Arc Enabled Kubernetes, which is to say a CNCF supported Kubernetes cluster running an Arc agent.
The dashboard is integrated with the Azure console, and displays resources at multiple levels, and displays configuration parameters. Cluster and workload monitoring is integrated with Azure Monitor.
Openshift is a self-serve Kubernetes management platform from Red Hat derived from the OKD open source Kubernetes distribution. It extends the Kubernetes project with several other projects to enhance enterprise readiness. Red Hat also offers managed Openshift deployments on Azure, AWS, and IBM Cloud. Multi-cluster management is provided by the Advanced Cluster Management tool. The tool lets users deploy workloads, apply security policies, and visualize operations across multiple Kubernetes clusters.
The dashboard provides a high level overview of health and usage, and enables users to dive into details from there. Clusters can be deployed on public and private clouds.
Rancher, is an open source software product focused on managing Kubernetes clusters. Rancher itself has no Kubernetes as a service offering. Instead Rancher offers automated Kubernetes installation and management on arbitrary compute nodes (Linux and Windows) and via managed service providers like EKS and GKE. Rancher provides multi-cluster management via a series of dashboards that span on-premises and cloud providers, offers workload deployment, and can unify RBAC across all. Rancher also offers a SaaS version of its product.
Rancher is pioneer in Kubernetes cluster management and puts more emphasis on management and visibility of clusters themselves, and less emphasis on workload management across clusters. A reasonable metaphor is that it is the equivalent of provider neutral cloud management platform (CMP) for Kubernetes.
Cloudify
Like Rancher, Cloudify is an open source multi-cluster management tool. Unlike Rancher, Cloudify doesn't limit it's management and orchestration capabilities to Kubernetes. Cloudify supports the major public cloud Kubernetes as a service providers like GKE, EKS and AKS, along with Helm3, Kubespray, and Openshift support for home grown clusters. By virtue of its unopinionated orchestration pedigree, it can manage multiple Kubernetes clusters, as well as a mixture of Kubernetes and non-Kubernetes services. Cloudify supports multicluster management by CLI and REST API, as well as a non-Kubernetes specific dashboard where Kubernetes clusters (and other managed entities) are presented in a drillable deployment list.
Cloudify provides multi-tenant and role based authentication capabilities, as well as support for day 2 operations across all managed services (Kubernetes and otherwise), including cascading and recurring workflows, state synchronization, and policy based workload placement. It also supports workload portability across Kubernetes platforms, enabling late binding of target environments.
Ready to see Cloud Native Transformation in action?
Download Cloudify now!
Kubernetes Governance & Cloud Native Migration Challenges
The complexity of securely managing even a single Kubernetes cluster can be challenging, let alone managing several. "Governance" here is defined as a practice of centralized control of cluster and workloads via policies. Policies are rules that dictate acceptable configuration ranges, communication security, user security, resource consumption, resource/user access, workload placement and other operational guardrails that can be applied across namespaces and clusters. Policies decouple governance from individual cluster configuration, reducing complexity especially at high scale.
Policies have both scopes (or restrictions), and targets. A scope defines the applicability of the policy, which limits the policy to a specific system domain like storage, users, application services, etc. The policy target is the specific resource in the domain (e.g. a user group, a network) that the policy is to be applied to. As far as policy management frameworks go, the CNCF has endorsed the Open Policy Agent (OPA) as a general purpose policy engine. Some high value targets for policies include:
Container images are the foundation of Kubernetes, and a potential source of great harm to any cluster. There are many compromised images on the internet, and verifying the validity of container images is a must for cloud native governance. Images must be from trusted sources, as well as scanned for vulnerabilities. Fortunately there are several image scanning products available (many open source), as well as support from Docker itself.
The management of certificates underpins network communication and user access. Certificate management encompasses the issuance, renewal, revocation, and installation of certificates. A certificate policy can govern all of these activities based on rules, for example whether to auto-renew a certain certificate.
As always, control of the network is fundamental to cluster security. Network governance includes inter-pod/service communication as well network access to clusters themselves. Internally, a service mesh (Linkerd, Istio) can be used to manage inter-pod network accessibility on the fly. Cluster isolation by its nature requires network automation external to Kubernetes itself.
Fine and Coarse Grained User Access
The management of user access both to the cluster itself and to individual objects in the cluster is a critical ongoing operational task. User access management is as old as the hills, of course. The ability to control user access at a very fine grained level (partially a result of the granularity of microservice architecture) makes it more complex than ever. Kubernetes provides a role based authentication implementation that can limit user access to resources in the cluster. Ultimately, high level user permissions and roles need to be translated into fine grained permissions, including limits on privilege escalation.
Cloud Native Migration Challenges
Moving from monolithic application architectures to cloud native architectures can be daunting. Cloud native doesn't mean package your monolith in a container, although many claiming the cloud native title do just that.
Cloud native architecture can be thought of as a three legged stool, each leg representing an operational goal:
High Availability – the application should be built to tolerate failure. Elements of a system should be able to fail (or be shut down, or moved ) randomly without causing system downtime. Many cloud migration challenges are a consequence of this goal.
Live Upgrades – the application should be able to be upgraded, downgraded, and patched without downtime. The ability to deliver customer value efficiently is a primary goal of cloud native architecture.
Business/Product Orientation – the application and related teams should be organized around business deliverables, not technology layers. The idea is that customer deliverables are correlated with the runtime services that deliver it, as well as the teams that provide it. This can be a challenge for organizations that organize teams based on technical expertise (database, UI, network, server, etc…).
For Kubernetes, the answer to support these goals is containers and a container management platform. In the abstract, containers are not required for a cloud native architecture, but Kubernetes is opinionated regarding containers, largely because of the agility they provide (extremely low overhead in both speed and memory domains).
Cloud native Kubernetes architecture organizes applications into loosely coupled services (the somewhat misnamed "microservices"), each with an independent life cycle. The granularity of these services is bespoke, based on the best organization to support the cloud native goals above. In general, the fewest number of services that are adequate to support the goals is ideal. Service proliferation is a source of great complexity (note the rise of the service mesh), and inter-service communication is slow, involving marshaling and network communication.
The typical migration process involves all three steps above in parallel, along with the learning curve associated with Kubernetes itself, which is significant even if you are outsourcing the management of your clusters. As adopting cloud native ultimately involves adjustments across the organization (imagine delivering software daily, or continuously), it can be daunting to consider.
A popular initial strategy to get various teams feet wet is to identify a candidate service in the monolith for cloud native implementation. Ideally this is a library or grouping of functionality that fits well behind a simple interface. Core logic for the service need not necessarily change (although it may), but the packaging will. You'll need to define an API (probably REST API) for the service, and make sure it can be relocated and restarted with full recovery. Then you'll need to write a client SDK. The monolith can then be altered to use the service. This exercise will build confidence and skills for the complete transformation.
General purpose tools like Cloudify can aid here, making it possible to incrementally migrate capabilities. This is made possible by the nature of a tool that can automate current tech stacks under the same umbrella as Kubernetes, and facilitate them working together. Perhaps the web tier goes first, as it is often easiest to make the cloud native transition. Later, other services can be added until the entire application is cloud native. It should be noted that the nature of cloud native applications also aids in making this possible, because of their fault tolerance: there should never be a "big bang" event when deploying a cloud native app. Microservices can be spun off from the monolith until the migration is complete.
Cloudify Kubernetes Multi-Cluster Use Cases
Cloud Native Application
Edge computing is a natural fit for the agility and high density of containerized solutions. Recently Cloudify demonstrated a Kubernetes based multi-cluster edge computing solution managing containerized network functions from F5, Intel QAT hardware acceleration, SR-IOV, CPU core pinning for pods, and more.
Beyond managing multiple Kubernetes clusters, Cloudify facilitates intelligent workload placement based on policies, for example placing workloads with very high performance requirements on clusters and nodes with appropriate hardware acceleration. Based on criteria such as location, resource availability, and special resource requirements, Cloudify provisions a workload to the correct Kubernetes cluster. Cloudify also supports deploying workloads across multiple clusters using a labeling system reminiscent of Kubernetes itself, the configuration of networking between clusters, and the execution of potentially complex, user defined, day 2 operations across clusters, both scheduled and ad hoc.
Driven by the low latency requirements of 5G wireless technology, and the resulting need for high density edge deployments, containers and Kubernetes has become a popular option for edge computing. The nature of 5G (short range: about 2% of 4G, obstacle sensitivity generally requiring line of sight) produces a need for far more antenna coverage than 4G, and anticipated applications (e.g. self driving cars, augmented reality) are forcing compute resources closer to the edge (i.e. users). If Kubernetes is running in those edge environments, then multicluster management is a critical part of the picture.
Cloudify and AT&T have collaborated on a cloud native edge solution for 5G along with the Linux Foundation ONAP project. The solution places Kubernetes clusters in edge sites running the ONAP Akraino stack for edge computing.
The architecture puts Cloudify in the role of multi-cluster manager for potentially large numbers of edge sites, providing edge stack deployment, self healing, and connecting edge sites with aggregated views provided by Grafana and Prometheus.
5G wireless communication requires edge computing, and pushes services closer to customers at the edge. From the operator perspective, it is desirable to deploy end to end isolated networks for service workloads. This need, and the rise of network function virtualization (NFV), has led to the concept known as 5G network slicing. Network slicing requires an orchestration software layer to manage the many configurations and deployments of virtual network functions (VNFs), and potentially related hardware configurations. In order to produce a 5G network slicing implementation, a broad range of services must be orchestrated, from Radio Access Network (RAN) to edge and core networks.
The ETSI Mano NFV architecture defines a layered orchestration model ( NFVO, VNFM ) to manage network functions. Cloudify assumed these roles and more in the implementation of 5G network slicing in AWS.
Cloudify, triggered by the ONAP SDC, orchestrated the end to end 5G network slicing implementation using AWS services including CodePipeline, CloudWatch, Lambda, and EKS hosted containerized network functions (CNFs) running on AWS Outposts. The user enters some parameters such as the slice edge location, slice differentiator, and slice domain. Slice orchestration included EKS cluster deployment, CNF instantiation/licensing, baseline configuration and day 2 operation.
The migration from monolithic to cloud native architecture and microservice oriented applications is steadily gaining steam. This transformation produces many benefits, including availability, scalability, portability, and seamless integration into modern agile development practices. These benefits come with costs though, mainly due to increased complexity both of the platform itself (Kubernetes usually), and microservices architecture itself. Layers of cloud native automation have emerged in industry to attempt to contain this complexity, including cluster deployment and management platforms from major cloud providers as well as cloud agnostic options.
As adoption of Kubernetes continues apace, the realization is growing that multi-cluster management is not an obscure edge case, but rather a standard feature of any reasonable delivery pipeline, independent of the applications being deployed. Beyond the single cluster application lies the multi-cloud/multi-cluster application that leverages multiple clouds and/or availability zones to exploit cloud provider features, lower costs, and achieve greater availability. Finally, few cloud native applications exist in a vacuum, but are integrated with non-cloud native legacy applications, which themselves require automation services.
For those with hybrid environments, Cloudify provides an unique value proposition because of its agnostic approach to orchestration. Multiple Kubernetes clusters, non-cloud-native services, cloud native infrastructure, Kubernetes lifecycle management, Kubernetes application lifecycle management, and legacy applications can be orchestrated under a single umbrella, with built in Gitops integration for end to end automation. Even for those who use a single cloud provider that provides multi-cluster Kubernetes tools, the use of an agnostic orchestrator like Cloudify reduces lock-in, and makes it possible to leave the door open to future multi-cloud opportunities when they arise.
Why Cloudify
Cloudify is a declarative, extensible, standards based, open source orchestrator built to provide automation for heterogeneous infrastructure and services. It integrates with all major cloud platforms out of the box ( AWS, Azure, GCP, VMWare, Openstack, etc..) and is highly customizable and adaptable for future technologies. Likewise, it integrates with existing tool chains beyond infrastructure, such as (CI/CD, Ansible, Kubernetes, Terraform, etc …). Its extensible, DSL vocabulary makes it easy to tailor to arbitrary use cases and levels of complexity, delivering a declarative everything as code experience. Also, the DSL is composable (not monolithic ), allowing for a microservices approach to orchestration automation.
Effortless transition to public cloud and cloud-native architecture by automating existing infrastructure alongside cloud native resources.
Break automation silos using an 'orchestrator of orchestrators' approach which can house all automation platforms (Kubernetes, Ansible, AWS Cloud Formation, Azure ARM, Terraform, etc.) under a common management layer. And be ready to incorporate new platforms and technologies as they appear.
Cost optimization by having end-to-end modeling of the entire infrastructure that enables cost-saving policies, such as decommissioning of resources. The decoupling of model from implementation in Cloudfy makes systems both more understandable and maintainable.
Reduced deployment time by bringing infrastructure, networking and security into reusable and 'templatized' environments, allowing deployment of a variety of tasks in hours rather than weeks, for applications that run on similar configurations. The composability of Cloudify templates makes it possible to abstract elements to their essentials so they can be substituted for each other; a form of polymorphism at the system level.
A highly customizable catalog and portal framework, built to provide a self-service experience that is tenant-aware. Not only customizable by selecting prebuilt "widgets" for inclusion in the console, but customizable via user defined widgets that can supply any user experience desired.
A horizontally scalable architecture that can support almost unlimited numbers of orchestrated resources. Open source. Not a black box that hides poor implementation, security holes, bugs, and closed to user contributions.
Hybrid-Cloud – a cloud solution or application that spans multiple public and/or private clouds.
Multi-Cloud – a cloud solution or strategy that utilizes on multiple cloud platforms, but doesn't combine them.
Public cloud – a (probably vast) collection of physical servers running virtual machines, that present the individual hardware as a single pool of compute, storage, and networking. Made available by the internet to the public via API and GUI. Examples include AWS, Azure, GCP, etc…
Private cloud – Like a public cloud, a collection of servers running virtual machines, presented as a single resource, but only made available internally to the enterprise. Examples include Openstack, Azure Stack, and VSphere.
Cloud Infrastructure – the "I" in "Iaas", cloud infrastructure refers to virtual networking, storage, and virtual machines (or containers) made available on demand via software (UI and API).
Continuous Integration (CI) – the practice of performing automated testing frequently on a code base. Testing is often triggered automatically by events in a version control system ( e.g. developer contributions/merges).
Continuous Delivery (CD) – the practice automated delivery of software to staging and/or production. Generally paired with continuous integration, but triggered by significant milestones (releases & bug fixes).
Declarative – As contrasted with imperative (or procedural), a way of programming by means of specifying desired outcomes via a model, as opposed to supplying a sequence of commands.
Service Orchestration – The deployment, updating, operation (scaling/healing), and decommissioning of software onto virtual or physical servers.
Container – an isolated execution environment in an operating system, a lightweight alternative to a virtual machine.
Virtual machine – a software emulation of a physical server.
Kubernetes – An open source container management platform that abstracts underlying hardware (virtual or physical), networking, and storage.
Data Center – A facility that hosts computer hardware. A data center centralizes compute capacity, and so is typically subject to stringent physical security and disaster/failover protections. Data centers are the building blocks of the cloud, and a failover pair of them can roughly map to availability zones in public clouds.
Availability Zone – A "virtual" data center that provides failover protection for high availability. An availability zone will typically consist of geographically separated data centers in a particular region.


Tharpu Chuli, also known as Tent Peak because of its shape, is situated near Annapurna Base Camp at an altitude of 5663m. The base of this peak is a short walk through the stunningly beautiful Annapurna Sanctuary. It is part of the ridge that extends south from glacier dome and includes another attractive and higher 6501m Singu Chuli or Fluted Peak peak directly above it.
The normal route to the summit is relatively easy but there is another challenging climb for those wanting to test their skills. This peak is not as high as other trekking peaks but the summit offers superb view of Annapurna I, Annapurna south, Annapurna III, Annapurna V, Machhapuchhare (Fish tail), Hiunchuli, Singu Chuli and Gangapurna.


text:
What Would You Do for a Klondike Bar?
Posted on June 3, 2011 by Laura Lippman
X-posted from Facebook Notes:
Alafair Burke's Duffer Awards poll — www.alafairburke.com — inspires me to share some of my more crazed foodie moments. In no particular order.
It was 2008 and I had to take a train to Bridgeport, CT, with my stepson because Mr. Lippman was in New York. Checking the train schedule, I realized that the Acela, which overshot Bridgeport, did stop in New Haven, which is said to be home to some of the country's best pizza. Why couldn't we rendezvous there and drive back to Bridgeport? We did and, because of our devotion to fair play in food tasting, we smuggled one pizzaria's slices into the other and ate them side by side.
We have done multiple cheese steak tastings in Philadelphia at Pat's and Geno's. The best one is inevitably the one we eat first.
Last weekend in Florida, we had to be at the airport, a 25 minute drive, by 1 p.m. The amazing sushi restaurant in our hotel opened at noon. Mr. Lippman and the stepson (called such because poor kid doesn't need me to embarrass him any more) hit the sushi restaurant at exactly noon, ordered sashimi and sushi and tartare while waiting for to-go order of the restaurant's version of "katsu," a minced beef sandwich that they happen to make with Kobe beef. It was like the Italian Job of foodie adventures.
Last month, we had promised to bring bagels and the proper accessories to a brunch in New York City. I walked 14 blocks north to Absolute Bagels, while Mr. Lippman took the subway to Russ & Daughters, then we met at our friends' apartment.
Leaving New York last summer, we went by way of Brooklyn to go to DiFara's pizza. It was closed for vacation. So we drove to Coney Island and went to Totonno's.
In 2006, when Bouchercon was held in Madison, I figured out it would be faster/easier to fly to Chicago and drive north. I persuaded four others to do the same — and made them all stop at Culver's, so I could have the cheese curds I remember so fondly from my summer camp days.
In 1981, my college friends and I went away for a weekend. We heard that Milwaukee had great ice cream, so we asked a nice police officer to guide us to a good place. One of my friends, whom I will not name here, was obsessed with trying the then-new confection known as a Twix Bar and I shot a photo essay of the momentous event.
1983, same friends, now in New Orleans: Despite meals at Galatoire's, Commander's Palace and the Acme, I still remember eating peanut M&M's while standing in line at Preservation Hall.
Summer of 2001: I flew to the Midwest to join Mr. Lippman and son on a baseball trip. They were dubious that someone with my credentials (an eating lightweight by their standards) could know anything of barbecue, but I told them that I had been reading Calvin Trillin since 1981 and wanted to go to Arthur Bryant's for a burnt-edges sandwich. The next day, when they dropped me at the airport, presumably en route to Iowa and the Field of Dreams, they immediately doubled back for another meal at Arthur Bryant's.
Taco Cabana. I went to the original, on Hildebrand and San Pedro, and while its proliferation as a chain was a boon in some ways, the original was special.
If I were on I-35 between Dallas and Waco, I would probably stop in West for kolaches.
Raised by a man who believed one must always make good time, married to a man who is profoundly unfamiliar with this concept, I'm never sure what to do when I pass the Kiwanis barbecue stands between Baltimore and the Delaware beaches.
I once had great Indian food in Laredo, Texas.
This entry was posted in The Memory Project by Laura Lippman. Bookmark the permalink.
12 thoughts on "What Would You Do for a Klondike Bar?"
Kevin C. on June 3, 2011 at 12:00 am said:
Man, I remember the Chicken Grilling along rt50 on summer Sunday afternoons in the 60′s on the way back to Bethesda from a Dewey Beach weekend. The smoke and smells from the grills would drift across rt50 and it was near impossible to not stop and get some.
I used to schedule air connections thru DCA so I could eat at Legal Seafoods, which is gone now. Now I get Legals in PHL where it is inside, not outside, security.
When I drive to the mid Atlantic now, I bring back 10lbs of sweet and hot sausage from Vace's on Connecticut Ave.
For many years there was a Taco Cabana in Ft. Wayne, of all places. I would often go out of my way to eat there. TC rocks. Calvin Trillin rocks too.
Marjorie of Connecticut on June 3, 2011 at 12:00 am said:
"…which is said to be home to some of the country's best pizza…"
Said to be? Said To Be?? I take umbrage. It is the best and I dare anyone to show me a finer thin crust pie anywhere. And who won (in your opinion, of course) Sally's or Pepe's? Of course I know the real answer to that question.
-Marjorie who lives spitting distance away from the country's best pizza
Laura on June 3, 2011 at 12:00 am said:
I can't remember who won. But I won't make a definitive comment on pizza until I've eaten at Chris Bianco's place in Arizona.
Bianco's pizza with red onion, parmigiano reggiano, rosemary and AZ pistachios was featured on The Best Thing I Ever Ate (as I recall) and it did look luscious. But can regular pizza and gourmet pizza be compared or are they apples and oranges?
Bianco makes a straight-forward pizza, too. He adapted the recipe for Gourmet and I've made it several times, with good results.
Jeff Abbott on June 3, 2011 at 12:00 am said:
If this writing thing doesn't work out for me my cunning plan is to take kolaches national. The Czech bakeries in West are very good, so are the kolaches at the Bon Ton Bakery in LaGrange, halfway between Austin and Houston. (I know, French-sounding bakery in a French-sounding town, but the recipe is pure Czech.) I used to stop on drives to Houston, get three for myself (cream cheese or peach or apple)-fresh from the oven-and then a packed dozen as a gift for my friends I was visiting.
Useless kolache-related trivia: Czech was once the third most spoken language in Texas.
Andi on June 3, 2011 at 12:00 am said:
I once had good authentic Mexican food in Racine, Wisconsin.
I used to ask friends to smuggle pounds of coffee in luggage when I was living in Boston. In the years between 1985 and 1990, until I moved back to the west coast, i was coffee-starved. As a coffee junkie, i suffered. Dunkin Donuts WAS okay for what it was, but I suffered.
However, at the same time, Bel Canto Pizza in Camridge offered amazing pizza and toppings and while it's hardly authentic, the turkey broccoli pizza on the pesto base and the garlic crust was pretty fine. I miss it.
As I miss Mary Chung. SO SO SO much. Last visit to Boston, i went there twice. And had the same thing. And i have the tee-shirt.
And last time i was flying out of Logan Airport in January, i had dinner at the airport Legal Seafood (there are restaurants now since they don't feed you on planes. It did not have the entire menu, which one local person was stunned at (he eats at LS a lot) but it was lovely.
I'm flying back east on Monday and am already planning on coffee and DD crullers for breakfast. Oooh, healthy!
Ab Logan on June 3, 2011 at 12:00 am said:
Pass on the Kiwanis chicken (get a gallon of their pickles if you're into pickles) but head west at Cambridge through Church Creek, past Blackwater to Wingate and have soft crabs right off the float. It's only an hour sidetrip.
Andi, I am sorry to report that you missed free donut day today (Friday) at Dunkin' Donuts. And if you were able to get to the New Haven area during your trip to Connecticut, I would bring you to a seafood shack that will make you happy as a clam. Pun intended!
brian stouder on June 4, 2011 at 12:00 am said:
If you ever spend a morning with the young folks tromping around with a map in hand, reading all the monuments and markers at Gettysburg - and then it becomes afternoon and you realize you're really hungry…
go back into town and head for Dobbin House (which is a beautful place in any case), and - whatever else you eat - order the French onion soup.
(and then report back)
Zelda on June 8, 2011 at 12:00 am said:
Whenever possible on my trips to visit family in MI, I'll fly into Chicago and drive the rest of the way so that I can stop at Bilbo's Pizza in Kalamazoo. It was my favorite 35 years ago and is still wonderful. I have good friends in Minneapolis who miss specific food items from Denver, so I've been known to get the Mexican Egg Rolls from The Pearl Street Grill and a pizza from Pasquini's and take them in my suitcase. Back before the ban on liquids, I'd also get Royal Crest Eggnog and carry it on the plane!
Jeff on June 25, 2011 at 9:13 pm said:
I'd do just about anything for a Klondike bar tbh

redpajama_set_name: RedPajamaCommonCrawl


text:
gambrell, joe (2)
mcdaniel, m. david (1)
dr. j.c. ayer & co. (1)
patient education -- methods (2)
pharmaceutical services (2)
advertising -- methods (1)
anesthetics;chloroform;menstruation-inducing agents;ether (1)
astringents (1)
hurricane hugo, 1989;medical university of south carolina;medical university of south carolina. medical university hospital;medical university of south carolina. children's hospital;hurricane hugo, 1989 -- personal narratives;disaster response and recovery (1)
pharmacy -- history (1)
pharmacy -- history -- 19th century (1)
All fields: pharmacist
Community pharmacist as a source of information for the patient
Gambrell, Joe
Patient Education--methods;Pharmacists;Pharmaceutical Services
Medical University of South Carolina. Board of Trustees;Medical University of South Carolina--Alumni and alumnae;Medical College of South Carolina--History--20th century;South Carolina Commission on Higher Education;Clemson University
Notes: Anesthetics
Anesthetics;Chloroform;Menstruation-Inducing Agents;Ether
Notes: Astringents
Hospital Herald, volume 2, number 1, January 1900
Association of Colored Physicians of South Carolina
African Americans--South Carolina--Periodicals;Education, Nursing--South Carolina--Periodicals;Association of Colored Physicians of South Carolina
Hospital Herald, volume 1, number 6, May 1899
Hospital Herald, volume 1, number 11, October 1899
Hospital Herald, volume 1, number 8, July 1899
Hospital Herald, volume 1, number 12, November 1899
Hospital Herald, volume 1, number 5, April 1899
The community pharmacist as a source of information for the patient by Joe Gambrell.
M. David McDaniel, oral history interview, 1 July 2009
McDaniel, M. David
Weather and medicine signals for daily reference
Dr. J.C. Ayer & Co.
Pharmacy--History;Pharmacy--history--19th century;Advertising--methods;Respiratory organs--Diseases--Treatment;Throat--Diseases--Treatment


First an amusement arcade, then a board game café and now the doors are opening to a huge pinball club in Croydon this weekend.
Matt Vince, 38, is one of ten pinball machine enthusiasts behind Flip Out London – a warehouse unit filled with 40 different pinball machines, some dating back to 1936 with other modern day versions such as Game of Thrones and The Simpsons.
The dad-of-three owns many machines and is now helping to open the doors to hundreds of enthusiasts and first time players.
Matt, a former Edenham High School student, said: "This is something I've wanted to do for a long time.
Matt's interest in pinball was inherited from his dad when he was a child, growing up in Croydon.
But as he entered his adult years, he said they appeared to "vanish from popular culture" and until his love was reignited when he worked in a bar that had a pinball machine in.
He has since gone on to organise more than 50 competitions for pinballers, has ran the London Pinball League for the last five years and his wife Sarah owns her own company supplying pinball machines and merchandise.
Matt originally tried to open a pinball club in Crawley, but when the opportunity fell through he said he almost "gave up" - until the space in Croydon became available.
The new club is thought to be one of the biggest in Britain – with the Electric Circus in Birmingham having about 30 machines, according to Matt.
The enthusiasm around competitive pinballing started in America and has since grown around the globe.
"Five years ago there was only one company making pinball machines and now there's about 10 around the world," explained Matt, who now lives in Crawley with his wife of three years and their children, Lucy, 6, Katie, 5, and two-year-old Daniel.
"A lot of the younger generation are interested. They have pinball games on their phones, and they want to play the real thing.
The 10 founders are even funding the new club from their own pockets, in a bid for it to be successful and eventually they hope it could be rented out for private parties.
Earlier this year, The Heart of Gaming, an amusement arcade, opened in the Whitgift Centre while this month the borough's first board game cafe The Ludoquist opened on High Street.
Flip Out London will be based at Unit 10, James Industrial Estate on Mill Lane in Croydon.
It is holding a grand opening this weekend on Saturday and Sundy (December 2 and 3) from 11am to 7pm. It will then be open every Thursday night and at the weekends.
Membership is £20 a month, which gives you free entry, or non-members can pay £10 on the door.


I have lost 76 pounds since January 1st and people are starting to notice. On one hand, it's very motivating that people are taking notice, on the other hand, it's kind of stressful and puts me in a position where I feel pretty awkward.
I don't feel awkward because someone notices that I lost weight, well that does make me feel a little awkward, but usually I feel awkward because the person I am talking to usually asks me what I am doing to lose so much weight and I am never really sure what to say. For instance, there is one lady who works on the same floor as I do that I really like, she and I have had some great conversations and she's just really nice. She and I passed in the hall on Friday and she told me that I looked good and asked me if I'd lost weight. I told her that I had lost about 75 pounds and she asked what I had been doing to get there. I told her that I was eating less and working out more, but then I felt bad because though that's true, that's not the whole truth, and continued to tell her that I had the surgery. My co-worker who was walking with me asked me afterward why I told people about the surgery and when I explained that I felt as if I was lying if I didn't, she explained to me that it wasn't a lie at all as I was eating less and working out more.
I know that there are some people who've had the surgery and will not tell anyone, and there are others who have had the surgery and will tell everyone. I think I may be middle of the road on this, but I do feel that not telling the whole truth is still a lie.
If you have had the surgery, what do you tell people who ask, and do you tell those who you really like more than those you just know in passing? I wonder if I am alone in my confusion.
It took me a while to tell people. I didn't tell my extended family until well after I had it. my coworkers are super nosey, so they noticed that first 30 pounds was gone and began to poke and prod for info. I actually couldn't really get through my pre-op diet without them asking me questions lol. The safe answer is the one you gave, though. Until I got comfortable talking about my surgery, I would say things like, "I've made big changes to my diet and I'm working out" or "Just trying to get my life together". Start sharing your experience when you're ready for all the commentary; both good and bad.


text:
Topic: COVID-19 Category: Review
Saeed S.
Neurospinal and Cancer Care Institute and Hospital, Karachi, Pakistan
soobiasaeed1@gmail.com Close
, Hashim A. S.
Neurospinal and Cancer Care Institute and Hospital, Karachi, Pakistan	Close
, Khan H.
OBJECTIVE: The existing facts on the traits of the unconventional coronavirus disease (COVID-19) Computerized Tomography (CT) scan with statistical results of tracking database are sent in specific journals, and a constant evaluation of the literature has not yet been compiled.
PATIENTS AND METHODS: COVID-19 disease, a systemic inflammation that impacts several organs, may be defined as a sickness that affects all age degrees, has a high mortality price, extreme negative results, and a chief economic burden. The Embase internet site, PubMed, OVID Medline, Cochrane Library, Science Direct, and Wiley became used to conduct a scientific assessment of these studies. COVID-19 patients' physiological acoustics are crucial for isolating them from other respiration infections. This report seeks to provide a summary of the Coronavirus epidemic, which has had a sizeable impact on humans' lives everywhere in the world. Plenty of humans have died, and the worldwide death rate from network-obtained pneumonia has reached three hundred million and continues to acquire pneumonia.
RESULTS: The most critical reason for shifting COVID-19 sufferers to the in-depth care unit is acute respiratory misery syndrome, which is likewise the leading motive of loss of life in these patients. COVID-19 sickness is thought to affect the blood vessels, lungs, heart, anxious gadget, liver, digestive system, kidneys, pores and skin, and other organs. Adults, infants, newborns, pregnant women, and the elderly are all infected, and it is spread through the air and droplets.
CONCLUSIONS: This systematic analysis of the latest literature on COVID-19 includes detail on the CT disease's baseline and follow-up characteristics.
Submission date: 20 Apr 2021
Revised on: 14 May 2021


text:
Hablainville je francouzská obec v departementu Meurthe-et-Moselle v regionu Grand Est. V roce 2013 zde žilo 217 obyvatel.

Poloha
Sousední obce jsou: Azerailles, Brouville, Buriville, Flin, Pettonville, Réclonville a Vaxainville.

Vývoj počtu obyvatel
Počet obyvatel

Odkazy

Reference

Související články
 Seznam obcí v departementu Meurthe-et-Moselle

Externí odkazy

Obce v departementu Meurthe-et-Moselle

redpajama_set_name: RedPajamaWikipedia


text:
Hitching in Marin during late 60s, early 70s
When I was a teenager, I bought my guitar stings from Van Morrison's mother at Caledonia Records in Fairfax.
It was worth the bother to get there as she'd make us a cuppa tea with shortbread. I was round-eyed—she sounded like my grannie but was from the north of Ireland. I looked for horns. We shared a name in common: Violet—but her fingernails and mouth were little scarlet wounds circling her cigarette.
Mr. Morrison, in his tweeds, was sitting on a stool, puffing away on his pipe, smiling at us from afar. Meanwhile one of Van's songs—maybe it was Gloria—was blaring on KFRC's Top Ten. I was learning Pastures of Plenty, and Cottenpicking—they chastizing me for not having a guitar case for such a valuable guitar.
One time she was shop-sitting for a friend at Amazing Grace Music, an old gas station cum music store on a tiny wedge of land between the Miracle Mile (Red Hill Ave.) and San Anselmo Avenue in San Anselmo. It was much farther out of the way for me so I rarely went there, but I had a Martin and I needed some Martin strings.
Mrs. Morrison made Van give me a ride home. Van the Man in the van was not pleased. He was seriously bent out of shape by the request so I was terrified to speak to him. And it was a long ride home held in utter silence. I lived far from town—way out in Forest Knolls, and he lived even farther out in Inverness.
There was no bus service out to The Valley so it was either thumb, or shank's mare. Van the Man drove a van. I had no real idea who he was at the time... I was so fecking shy I couldn't talk to him even if I wanted to.
It seems that every rock musician from the 60s moved out to West Marin—sort of a fallout from the Haight. West Marin was invaded by the likes of the Sons of Champlin, Big Brother & the Holding Company, Grateful Dead, Jefferson Airplane—to name a few.
They saw us kids hitching home every day—to us, it was merely an alternate bus service. We didn't think twice that these guys were famous. The road out to The Valley was long and winding, and in those days, people generally stopped for hitchikers.
Jesse Colin Young, who also lived in Inverness, was much easier to talk to than Van. He had cute little kids who took swimming lessons with ze French Mrs. Zettl who lived half way up Arroyo Road—so I got a ride almost all the way home from Jesse.
Carlos Santana was silent like Van—absolute mauna. He had a nice Mercedes with fawn leather seats though... One morning, I was still half-asleep, hitching into Drake High School (emphasis at that point was on getting high), Carlos pulled over to offer me a lift.
It was pretty early so Carlos might not have been awake either. He was pulling pretty hard on both his coffee mug and a joint. He looked half-dressed—like he just rolled out of bed. I remember being a little shocked that he wore those baggy string pants. Them string pants were riding dangerously low on Carlito's hips as I recall....
Carlos moved into my friend Lindy Young's place on Tamal Road (right up from Linda Gregg's place—where Jerry Garcia later died) and he had horses too—that was our common ground. I don't remember much else—other than I got to school on time.
Got a ride from decopage artists Larry Fuentes and Dickens Bascom too. Dickens' art car had an entire Remington typewriter that still worked glued to the trunk of his Fort Falcon. The sides and fins were lined with worn out sneaker bottoms—like fish scales. Poetic justice.
My College of Marin classmate David Best copied Dickens Bascom and Larry Fuentes' art-cars and came up with some amazing art-cars of his own—and made a career of it. I loved the flocked chia seed Cadillac punctuated with mirror shards and a water buffalo head hood ornament that he used to park at Micky McGowan's Unknown Museum in Mill Valley.
The Unknown Museum, (founded ca. 1974—but I think it was earlier than that) which closed its doors in 1989, was something to behold with all its repurposed Americana detritus as iconography—the ultimate recycler's wetdream.
David told me that at night the deer came down to graze on the car. Mickey the cobbler had a Fiat stuffed with Disney toys and Barbie dolls.The Fiat didn't run, but David's Caddy did—I sat in it with David and talked until the cows came home, but never got a real ride in it. So I guess it doesn't count. Somewhere I have the slides... fodder for another blog.
One time Dickens and Larry hauled a découpaged life-size fiberglass model horse out to a pond where the Dollar house once stood—on the San Geronimo Golf Course. I had my camera with me (and a fresh roll of Kodachrome) so I stuck around. They did a great Lady Godiva number at sunset. The girl wore a red cape and a fierce mane of red hair. Not much else. People nearly drove off the road. But I still had to walk all the way back home to Forest Knolls from San Geronimo. No one would stop along that section of road. Shank's mare.
I never got a photo of Dickens' art car, but I did manage to document his horse at the San Geronimo Golf Course. But Long's Drugs Kodak developer sliced all my negatives in two lengthwise. I was able to salvage a few sliced photos (magically healed with a cloning tool).
See Paul Liberatore's article on Mickey McGowan in Exhibit of 55 recycled, reused artworks gets once-over from Mill Valley's Unknown Museum's ex-curator
Somewhere in all this thumbin- for-a-ride business, I actually owned a car, or rather, a funky 1958 panel Singer Sewing Machine Volvo van that my uncle gave me—but keeping it running was a full-time occupation. The carburetor linkage was held together with baling wire because I couldn't find the parts. So I was often car-less. David Best wanted to découpage it. But I let it rot into the hillside when it died, thinking I would revive it someday—like Kesey's bus, Further. But the spare parts were just too hard to find.
Ken Kesey stopped for me in Fairfax on The Magic Bus, or was it Further? We generically called it the magic bus but its destination was further. Now, that was one way cool ride. The Merry Prankster himself grabbed the hand door crank and opened the glass doors and said with a huge grin, "Climb aboard!" Kesey's original Further (not Further 2) was like an old Bluebird schoolbus, like the mad buses in Guatemala.
Not only was the outside painted in rainbow hues, the entire inside of the old yellow bus was psychedelically painted and collaged. It was another world. I was like Alice down the rabbithole. I pretty much had the bus to myself. So I migrated up and down the aisles, sitting here and there, checking out the artwork. Lots of music posters from FIllmore and Winterland daze.
Some dude was splayed out, smokin' in the back seat with friends. I believe courtesy inhaling was involved. BTW, Ken Kesey pulled over for everybody who was hitching. So it took a very long time to get home.
Years later (ca. 1976), Ken Kesey told me that the fabled old bus was mouldering away in his lower south 40 field in Pleasant Hill, Oregon. He was doing a magazine called Spit in the Ocean and I was working for the Western Star Press selling tarot cards, of all things. Rosalind Sharpe Wall and John Starr Cooke made a New Age Tarot deck, The New Tarot: a deck for the Aquarian Age (1969). Ken wanted to buy some tarot cards.
It sold for $8
On Amazon now for $125+
During the mid-1970s I worked for Alice Cooke Kent at Western Star Press. I had to hand-sorted every 78-card deck I sold as the printer had a major collating fuckup. The decks arrived loose, jumbled in big boxes—it was like a colossal 52-card pick-up party. I sorted so many decks, I was stacking major arcana in my sleep. They're imprinted indelibly into memory. Rosalind Sharpe Wall, the artist, was my friend Miranda Micaela's mom. She and my mom, who also designed a deck—were arch enemies. So I was working for the opposition.
I was loath to cash that small check with that famous Ken Kesey signature on it. We struck up a correspondence of sorts and he sent me some signed books. I'd give my eye teeth and molars to have them now. I wasn't yet a poet, so I didn't pay close attention. Didn't take notes. Didn't listen to the music of the words that were coming unbidden.
Labels: Carlos Santana, David Best, Dickens Bascom, Further, Jesse Colin Young, John Cooke, Ken Kesey, Larry Fuente, Rosalind Sharpe, San Geronimo Valley, Unknown Museum, Van Morrison
$5revolutions said...
I still own a pair of boots made by Micky the Apple Cobbler
Maureen Hurley said...
I would love to see a photo of them, if you have one.
Brownie Mary
On my broken nose
On Sáami Culture
THE SOUL TRUTH, AND NOTHING BUT
Goldfish —After Frank O'Hara
Fundraiser for Lagunitas Montessori, Point Reyes S...
Bantry cousins


text:
The Aviation Industry Hub
Event Wraps
FIA Connect Hub
Business & General Aviation
Engines / Propulsion
From The TopEvent WrapsLeadershipInnovation & TechnologyRegulationAviation ServicesBusiness & General AviationSpaceUnmannedAir TransportManufacturingDefenceRotorcraftEngines/Propulsion
I have read and understood the privacy policy
Boeing and Kitty Hawk form strategic partnership
Tags: Boeing, Boeing NeXT, Kittyhawk, Urban air mobility
Boeing and Kitty Hawk Corporation have announced a strategic partnership to collaborate on urban air mobility.
Boeing and Kitty Hawk Corporation have announced a strategic partnership to collaborate on urban air mobility. Details about what the collaboration will involve were scant at this stage.
Kitty Hawk Corp., headquartered in Mountain View, California, is developing the Cora two-person air taxi, and Flyer, a vehicle for personalised flight. The aircraft will be offered via services rather than directly to customers.
The Cora has reportedly performed well in tests, reports say, and can fly at speeds of around 110 miles per hour at 500 to 3,000 feet. However, the company has no schedule for launch yet, saying: "We are not putting timeframes around when Cora will be available for public flight. We have a lot of work to do and we are working constructively with regulatory authorities. We are looking forward to being able to share our product with the New Zealand public when the time is right."
"Working with a company like Kitty Hawk brings us closer to our goal of safely advancing the future of mobility," said Steve Nordlund, vice president and general manager of Boeing's innovation arm, Boeing NeXt.
"We have a shared vision of how people, goods and ideas will be transported in the future, as well as the safety and regulatory ecosystem that will underpin that transportation," Nordlund said.
"Kitty Hawk was started to advance technology in flight and bring new innovations to life," commented Sebastian Thrun, co-founder and CEO of Kitty Hawk. "I am excited about our companies working together to accelerate making safe, electric flight a reality."
The Global Urban Air Summit will be an elite gathering of innovators, regulators, government and investors who will address the global challenges in urban air mobility, showcase the latest innovations and truly shape the future of air travel.
Siemens and Sonaca win additive manufacturing contract from European Space Agency
FAA finds new potential issue with Boeing's 737 MAX
Explore Our Other Topics
Engines/Propulsion
Copyright © 2021 FINN
This policy explains how Farnborough International Limited of Show Centre, ETPS Road, Farnborough, GU14 6FD ("we" or "us") uses any personal information which it collects about you when you use our websites.
WHAT INFORMATION DO WE COLLECT ABOUT YOU
Information that you provide by filling in forms on our sites farnborough.com, https://www.farnboroughairshow.com, farnboroughinternational.org and https://www.wearefinn.com ("our site(s)"). This includes information provided at the time of placing an order for our services, subscribing to our service, posting materials or requesting further services. We may also ask you for your personal data when you enter our competition, complete customer surveys, or contact us with any enquiry. Website usage information including traffic data, location data, weblogs, your domain name and your email address and other communication data is collected using cookies as per the following cookies policy.
HOW DO WE USE YOUR PERSONAL INFORMATION
We process your personal data to process and fulfil your order or deliver the services you signed up for, manage your account, answer enquiries, email you about products and services which may be of interest to you and notify you about changes to our service. We will keep your personal data for a maximum period of 7 years from the time you last contacted us. We use your personal data collected from our websites usage to track activities on our website and ensure that content from our site is tailored in the most effective manner for you and for your computer. We will keep your website usage data for the time prescribed in our cookies policy.
We may disclose your personal information to third parties as follows: - to our contractors helping us to deliver our services to you. - to comply with any legal obligation, or in order to enforce or apply our terms of use and other agreements or to protect our rights, property, or safety of our visitors, our customers, or others. This includes exchanging information with other companies and organisations for the purposes of fraud protection and credit risk reduction. - We do not process your data outside of the European Union.
You have the right to ask us not to process your personal data for marketing purposes. If you no longer wish to be contacted for marketing purposes, please email us at optout@farnborough.com. You have the right to request a copy of the information that we hold about you. If you wish to do so, please email us at mydata@farnborough.com. You may ask us to correct or remove information which you think is inaccurate. To request a removal or correction of your personal information, please email us at mydata@farnborough.com. You have the right to lodge a complaint about our processing of your personal information with the Information Commissioner's Office.
Any changes we may make to our Privacy Policy in the future will be posted on this page and, where appropriate, notified to you by email. This Privacy Policy was last updated on 1 May 2018.
Our site may contain links to and from the websites of our partner networks, advertisers and affiliates. If you follow a link to any of these websites, please note that these websites have their own privacy policies and that we do not accept any responsibility or liability for these policies. Please check these policies before you submit any personal data to these websites.
Questions, comments and requests regarding this privacy policy are welcomed and should be addressed to [email protected] or send per post to our address Farnborough International Limited of Show Centre, ETPS Road, Farnborough, GU14 6FD
Please confirm that you agree to our privacy policy


Work Together To Keep the Island From Sinking!
This was our family's first foray into the world of cooperative board games - meaning everyone wins or everyone loses. You must work together to collect treasures and keep the island from sinking. Recommended for 10 and up, and there's many variants to how you play - you can layer in more twists and difficulties as you get used to the game. Great game to play with different age levels.


text:
Bill Davidson (1947–2003) was born on 12 October 1947 in Alberta, Canada, and grew up in an orphanage. Bill was a pioneer in the Canadian rock climbing-scene during the 1970s. After an early free ascent of the North America Wall of El Capitan, Yosemite National Park, in 1970, Bill returned to his native Alberta where he introduced extreme climbing to the Canadian Rockies. Around 1975, Bill suffered a near-fatal fall and left the climbing scene. On a visit to British Columbia, he purchased a green and white double Frontiersman kayak, reduced his belongings to what he could carry with him, and traveled the north coast of British Columbia establishing campsites on many remote islands. "Kayak" Bill often spent winters in Sointula on Malcolm Island where he became a self-taught "outsider" artist—painting fanciful watercolors during the winter months and selling his paintings to purchase supplies for his kayaking travels.

Kayak Bill Davidson died in December 2003, while camping in the Goose Islands group near Hakai, British Columbia.  He made daily journal entries and on 6 December he mentioned experiencing "lower back & stomach pains".  His last entry was made the next day on 7 December.  It is believed that he died on 8 December 2003. Bill is survived by one son, Westerly Davidson.

Notable ascents
 1970 North America Wall of El Capitan, Yosemite, CA, USA.
 1971 Wakonda Buttress of Yamnuska, Kananaskis, AB, Canada.
 1971 North Face of Gibraltar Mountain, Kananaskis Country, Alberta, Canada.
 1972 CMC Wall on Yamnuska, Kananaskis, AB, Canada.
 1974 Yellow Edge on Yamnuska, Kananaskis, AB, Canada.

References

1947 births
2003 deaths
Canadian rock climbers


Marlene Reid DPM, FACFAS, FASPS is a spokesperson for the American Podiatric Medical Association (APMA) and expert on women's foot health and shoes. She is a former chair of the APMA's Public Education Committee, past president of both the Illinois Podiatric Medical Association (IPMA) and the American Association for Women Podiatrists and currently IPMA Trustee, APMA Delegate, Illinois Licensing Board member and National Association of Practitioners. Podiatric Chair. Dr. Reid practices in Naperville, IL with her husband at Family Podiatry Center.
Articles approved by Marlene Reid, D.P.M.


23/09/2011 · This tutorial shows six fundamental MATLAB functions to use in image processing. The code can be found in the tutorial section in http://www.eeprogrammer.com/. how to make rfid tag and reader 2/08/2013 · The 3rd session of the Introduction to image processing using MATLAB in which we read color images.
Most likely, you won't be able to extract the image from the pdf. The pdf format is designed for consumption by humans, not by computers. Depending on how the image is actually stored in the pdf it would be difficult to downright impossible to extract it.
I read in lena.jpg and wrote out lenna (no file extension) from it using fwrite(). I then used the code you indicate to read it back in, changing only the path to the file. It works for me and produces an input identical to the original.
Some neighborhood operations work with the values of the image pixels in the neighborhood and the corresponding values of a sub image that has the same dimensions as the neighborhood.
Is lena.jpg available for matlab? It would be nice for matlab to incorporate the computer vision/image processing standard picture, in some lossless format, for testing.
Read in an RGB image, and display it using imshow. Using the "Data cursor" tool under "Tools" in the Using the "Data cursor" tool under "Tools" in the display window, pick a few points and find out their location and R,G,B values.