53 new things to look for in OpenStack Newton

The post 53 new things to look for in OpenStack Newton appeared first on Mirantis | The Pure Play OpenStack Company.
OpenStack Newton, the technology&;s 14th release, shows just how far we&8217;ve come: where we used to focus on basic things, such as supporting specific hypervisors or enabling basic SDN capabilities, now that&8217;s a given, and we&8217;re talking about how OpenStack has reached its goal of supporting cloud-native applications in all of their forms &; virtual machines, containers, and bare metal.
There are hundreds of changes and new features in OpenStack Newton, and you can see some of the most important in our What&8217;s New in OpenStack Newton webinar.  Meanwhile, as we do with each release, let&8217;s take a look at 53 things that are new in OpenStack Newton.
Compute (Nova)

Get me a network enables users to let OpenStack do the heavy lifting rather than having to understand the underlying networking setup.
A default policy means that users no longer have to provide a full policy file; instead they can provide just those rules that are different from the default.
Mutable config lets you change configuration options for a running Nova service without having to restart it.  (This option is available for a limited number of options, such as debugging, but the framework is in place for this to expand.)
Placement API gives you more visibility into and control over resources such as Resource providers, Inventories, Allocations and Usage records.
Cells v2, which enables you to segregate your data center into sections for easier manageability and scalability,has been revamped and is now feature-complete.

Network (Neutron)

802.1Q tagged VM connections (VLAN aware VMs) enables VNFs to target specific VMs.
The ability to create VMs without IP Address means you  can create a VM with no IP address and specify complex networking later as a separate process.
Specific pools of external IP addresses let you optimize resource placement by controlling IP decisions.
OSProfiler support lets you find bottlenecks and troubleshoot interoperability issues.
No downtime API service upgrades

Storage (Cinder, Glance, Swift)
Cinder

Microversions let developers can add new features you can access without breaking the main version.
Rolling upgrades let you update to Newton without having to take down the entire cloud.
enabled_backends config option defines which backend types are available for volume creation.
Retype volumes from encrypted to not encrypted, and back again after creation.
Delete volumes with snapshots using the cascade feature rather than having to delete the snapshots first.
The Cinder backup service can now be scaled to multiple instances for better reliability and scalability.

Glance

Glare, the Glance Artifact Repository, provides the ability to store more than just images.
A trust concept for long-lived snapshots makes it possible to avoid errors on long-running operations.
The new restrictive default policy means that all operations are locked down unless you provide access, rather than the other way around.

Swift

Object versioning lets you keep multiple copies of an individual object, and choose whether to keep all versions, or just the most recent.
Object encryption provides some measure of confidentiality should your disk be separated from the cluster.
Concurrent bulk-deletes speed up operations.

Other core projects (Keystone, Horizon)
Keystone

Simplified configuration setup
PCI support of password configuration options
Credentials encrypted at rest

Horizon

You can now exercise more control over user operations with parameters such as IMAGES_ALLOW_LOCATION, TOKEN_DELETE_DISABLED, LAUNCH_INSTANCE_DEFAULTS
Horizon now works if only Keystone is deployed, making it possible to use Horizon to manage a Swift-only deployment.
Horizon now checks for Network IP availability rather than enabling users to set bad configurations.
Be more specific when setting up networking by restricting the CIDR range for a user private network, or specify a fixed IP or subnet when creating a port.
Manage Consistency Groups.

Containers (Magnum, Kolla, Kuryr)
Magnum

Magnum is now more about container orchestration engines (COEs) than containers, and can now deploy Swarm, Kubernetes, and Mesos.
The API service is now protected by SSL.
You can now use Kubernetes on bare metal.
Asynchronous cluster creation improves performance for complex operations.

Kolla

You can now use Kolla to deploy containerized OpenStack to bare metal.

Kuryr

Use Neutron networking capabilities in containers.
Nest VMs through integration with Magnum and Neutron.

Additional projects (Heat, Ceilometer, Fuel, Murano, Ironic, Community App Catalog, Mistral)
Heat

Use DNS resolution and integration with an external DNS.
Access external resources using the external_id attribute.

Ceilometer

New REST API that makes it possible to use services such as Gnocchi rather than just interacting with the database.
Magnum support.

FUEL

Deploy Fuel without having to use an ISO.
Improved life cycle management user experience, including Infrastructure as Code.
Container-based deployment possibilities.

Murano

Use the new Application Development Framework to build more complex applications.
Enable users to deploy your application across multiple regions for better reliability and scalability.
Specify that when resources are no longer needed, they should be deallocated.

Ironic

You can now have multiple nova-compute services using Ironic without causing duplicate entries.
Multi-tenant networking makes it possible for more than one tenant to use ironic without sharing network traffic.
Specify granular access restrictions to the REST API rather than just turning it off or on.

Community App Catalog

The Community App Catalog now uses Glare as its backend, making it possible to more easily store multiple application types.
Use the new v2 API to add and manage assets directly, rather than having to go through gerrit.
Add and manage applications via the Community App Catalog website.

Did we miss your favorite project or feature?  Let us know what new features you&8217;re excited about in the comments.
The post 53 new things to look for in OpenStack Newton appeared first on Mirantis | The Pure Play OpenStack Company.
Quelle: Mirantis

Why businesses shouldn’t settle on a storage solution

To date, the business community, including startups and entrepreneurs, have had only simple storage solutions to choose from on the cloud. Or they’ve had outdated, pricey software, hardware and appliance solutions from legacy storage providers.
In today’s business world, this no longer works. Not with IDC’s predicted data growth of 44 zettabytes by 2020, fueled by the increased use of cloud, mobile, analytics, social and even cognitive to drive digital transformation. Additionally, unstructured content (images, video, audio, documents, and so on) outnumbers structured content by a factor of four.
In this world, simple storage solutions fall short. Governments and clients have increased pressure to assure compliance and residency requirements for content and applications. Transparency and coverage are not always strengths of cloud solutions.
Businesses shouldn’t have to settle for a simple cloud storage option. That’s why IBM Cloud Object Storage offers flexibility, scalability and simplicity. Solutions can be deployed on premises and across the IBM Cloud with more than 45 data centers around the world. Users get full transparency and control.
That’s essential because business is intrinsically hybrid. Elements of hybrid business processes require that some applications and content run on premises for performance, compliance or simply colocation with compute resources. Other business processes are well supported with either a dedicated or shared object storage deployment on IBM Cloud. IBM Cloud Object Storage supports both Amazon S3 and OpenStack Swift across deployment models, so there’s a consistent technology platform to support your applications and initiatives.
Additionally, there’s a higher level of availability and security. IBM Cloud Object Storage takes data that lands on one region on the IBM Cloud, then slices, erasure-codes and disperses the slices across three regions using something called SecureSlice.
Why does that matter? Two reasons:

If security is compromised in a region, the full content will not be exposed.
If one region is offline, your applications continue to run without disruption and without you having to intervene.

The IBM Cloud Storage approach translates to significantly better economics. Prices are over 25 percent less than other cloud storage providers*.
But the really exciting part goes beyond IBM Cloud Object Storage and layers on other IBM capabilities. Think of the exciting technology emanating from IBM Watson, IBM Bluemix and IBM Cloud Video Services. Cognitive will be essential as data grows from tera- to peta- to exa- to zettabytes, in the process taxing out ability to manage and utilize this growing mountain of content.  There is even broader value if you look at the IBM Spectrum family, with transparent cloud tiering and beyond. It is truly an exciting tapestry that you can weave together to elevate your .
Our ecosystem of partners delivers even more innovation and value. Our channel is broad, but to understand what’s possible, just look at what  the likes of Panzura, Nasuni, Mark III and CTERA are doing in bringing our portfolio, along with their expertise and IP, to deliver even greater value.
Learn more about IBM Cloud Object Storage and how it can be employed in your organization.
* Comparison is between IBM Cloud Object Storage Vault Cross-Region and S3 Infrequent Access bucket in AWS US East with Cross Region Replication to S3 Infrequent Access bucket in US West Oregon. Pricing is based on published IBM and Amazon US list prices as of October 13, 2016. Price includes storage capacity, API operations, internet data transfer charges, and cross-region data replication charges (s3 only). Pricing will vary depending on workload capacity, object size, data access patterns, and configuration. Pricing for this comparison based on the following workload assumptions:

Mixed footprint of 50 percent &;small&; and 50 percent &8220;large&8221; objects (by capacity). Average object sizes: small = 1GB, large = 5GB.
Monthly access pattern for all &8220;small&8221; and “large” objects: 10 percent read, 50 percent written, 5 percent listed, All objects assumed retained at least 30 days.
All object reads assumed outbound to internet (internet data transfer charges apply for all GETS).

The post Why businesses shouldn’t settle on a storage solution appeared first on news.
Quelle: Thoughts on Cloud