Openstack IPv6 and Liberty (or Mitaka). Simon Leinen Sun Oct 30 21:25:05 UTC 2016. Previous message:. Next message:.

1. Openstack Liberty Download For Machine

The official OpenStack Liberty Install Guides are a great way to get hands-on experience with installing and configuring OpenStack by hand. This post describes how to install and configure a local VirtualBox environment for performing the step-by-step deployment instructions found in the guide. Apr 25, 2016 - HowTo Install Mellanox OpenStack Plugin for Mirantis Fuel 8.0. We recommend that you record the MAC address of the Controller and Storage. In Liberty each VM can start by using either the standard Para-Virtual.

Messages sorted by: Ken D'Ambrosio writes: Hey, all. I have a Liberty cloud, and decided for the heck of it to start dipping my toe into IPv6.

I do have some confusion, however. I can choose between SLAAC, DHCPv6 stateful and DHCPv6 stateless - and I see some writeups on what they do, but I don't understand what differentiates them. As far as I can tell, they all do pretty much the same thing, just with different pieces doing different things. E.g., the chart, found here ( - page down a little) shows those three options, but it isn't clear:.

How to configure the elements involved. What they exactly do (e.g., 'optional info'? What's that?). Why there even.are. different choices. Do they offer functionally different results? SLAAC and DHCPv6-stateless use the same mechanism (SLAAC) to provide instances with IPv6 addresses.

The only difference between them is that with DHCPv6-stateless, the instance can also use DHCPv6 requests to get other information such as nameserver addresses etc. So choosing between SLAAC and DHCPv6-stateless, I would always prefer DHCPv6-stateless - it's a strict superset in terms of functionality, and I don't see any particular risks associated with it.

DHCPv6-stateful is a different beast: It will use DHCPv6 to give an instance its IPv6 address. DHCPv6 actually fits OpenStack's model better than SLAAC1.

Unfortunately, most GNU/Linux distributions don't support Stateful DHCPv6 'out of the box'. Because we want our users to use unmodified operating systems images and still get usable IPv6, we have grudgingly decided to go for DHCPv6-stateless. For configuration information, see2. If you decide to go for DHCPv6-stateful, then here's a Web page that explains how to enable it client-side for a variety of GNU/Linux distributions: It would be nice if all systems honored the 'M' (Managed) flag in Router Advertisements and would use DHCPv6 if it is set, otherwise SLAAC.

Any pointers would be much appreciated. While I was able to get a host up with IPv4/IPv6, I wish I understood more of what was going on behind the scenes. Hope this helps, 1 What I mean is this: OpenStack (Nova) sees it as part of its job to control the IP address(es) that an instance uses. In IPv4 it uses DHCP (always did). DHCP assigns complete addresses - which are under control of OpenStack. In IPv6, stateful DHCPv6 would be the proper equivalent.

SLAAC is different in that the node (instance) actually chooses its address based on information it gets from the router. The most common method is that the node uses an 'EUI-64' address as the local part (host ID) of the address.

The EUI-64 is derived from the MAC address by a fixed algorithm. This can work with OpenStack because OpenStack controls the MAC addresses too, and can thus 'guess' what IPv6 address an instance will auto-configure on a given network. You see how this is a little less straightforward than OpenStack just.telling. the instance what IPv6 address it should use. In practice, this breaks down when an instance uses other methods to get the local part, for example 'privacy addresses' according to RFC 4941. These will lead to conflicts with OpenStack's built-in anti-spoofing filters.

So such mechanisms need to be disabled when SLAAC is used under OpenStack (including under 'DHCPv6-stateless'). 2 - Simon. Previous message:.

Next message:. Messages sorted.

Rocky (2018.08.30) / 30 August 2018; 3 months ago ( 2018-08-30) Written in 2.0 Website OpenStack is a and for, mostly deployed as (IaaS), whereby virtual servers and other resources are made available to customers. The software platform consists of interrelated components that control diverse, multi-vendor hardware pools of processing, storage, and networking resources throughout a. Users either manage it through a web-based dashboard, through tools, or through web services. OpenStack began in 2010 as a joint project of. As of 2016, it is managed by the OpenStack Foundation, a non-profit corporate entity established in September 2012 to promote OpenStack software and its community.

More than 500 companies have joined the project. NASA's platform In July 2010, and jointly launched an open-source cloud-software initiative known as OpenStack. The mission statement was 'to produce the ubiquitous Open Source Cloud Computing platform that will meet the needs of public and private clouds regardless of size, by being simple to implement and massively scalable'. The OpenStack project intended to help organizations offer cloud-computing services running on standard hardware.

The community's first official release, code-named Austin, appeared three months later on 21 October 2010 ( 2010-10-21), with plans to release regular updates of the software every few months. The early code came from NASA's platform as well as from.

The original cloud architecture was designed by the NASA Ames Web Manager, Megan A. Eskey, and was a 2009 open source architecture called OpenNASA v2.0. The cloud stack and open stack modules were merged and released as open source by the NASA Nebula team in concert with Rackspace. In 2011, developers of the Linux distribution adopted OpenStack with an unsupported technology preview of the OpenStack 'Bexar' release for Ubuntu 11.04 '. Ubuntu's sponsor then introduced full support for OpenStack clouds, starting with OpenStack's Cactus release.

OpenStack became available in from the Openstack 'Cactus' release in 2011, and the first release of Debian including OpenStack was Debian 7.0 (code name 'Wheezy'), including OpenStack 2012.1 (code name: 'Essex'). In October 2011, announced the public preview of the industry's first fully configured OpenStack powered appliance based on the 'Diablo' OpenStack release. In August 2012, SUSE announced its commercially supported enterprise OpenStack distribution based on the 'Essex' release. In November 2012, The UK’s (GDS) launched Inside Government based on the OpenNASA v2.0 Government as a Platform (GaaP) model. Lew Tucker, VP & CTO, Cloud Computing of Cisco in 2012 In 2012, Red Hat announced a preview of their OpenStack distribution, beginning with the 'Essex' release. After another preview release, Red Hat introduced commercial support for OpenStack with the 'Grizzly' release, in July 2013.

The OpenStack organization has grown rapidly and is supported by more than 540 companies. In 2012 NASA withdrew from OpenStack as an active contributor, and instead made the strategic decision to use for cloud-based services. In July 2013, NASA released an internal audit citing lack of technical progress and other factors as the agency's primary reason for dropping out as an active developer of the project and instead focus on the use of public clouds.

This report is contradicted in part by remarks made by CIO, Ray Obrien. In December 2013, Oracle announced it had joined OpenStack as a Sponsor and planned to bring OpenStack to Oracle Solaris, Oracle Linux, and many of its products. It followed by announcing Oracle OpenStack distributions for Oracle Solaris and for Oracle Linux using Icehouse on 24 September 2014. In May 2014, HP announced and released a preview of HP Helion OpenStack Community, beginning with the IceHouse release. HP has operated HP Helion Public Cloud on OpenStack since 2012. At the 2014 and, software-defined networking was demonstrated by using and OpenStack as an automated campus, extending automation from the data center to the end device, removing manual provisioning from service delivery. As of March 2015, NASA still makes use of OpenStack private cloud and has out for OpenStack public cloud support.

OpenStack development The OpenStack community collaborates around a six-month, with frequent development milestones. During the planning phase of each release, the community would gather for an OpenStack Design Summit to facilitate developer working sessions and to assemble plans. These Design Summits would coincide with the OpenStack Summit conference. Starting with the Pike development cycle the design meetup activity has been separated out into a separate Project Teams Gathering (PTG) event.

This was done to avoid the developer distractions caused by presentations and customer meetings that were happening at the OpenStack Summit and to allow the design discussions to happen ahead of the start of the next cycle. Recent OpenStack Summits have taken place in on 21-25 May 2018, Sydney on 6-8 November 2017, on 8-11 May 2017, on 25–29 April 2016, and on 25–28 October 2016. Earlier OpenStack Summits have taken place also in in October 2015, in May 2015, and in November 2014. The summit in May 2014 in drew 4,500 attendees — a 50% increase from the summit six months earlier.

Components. OpenStack main services OpenStack has a modular architecture with various code names for its components.

Compute (Nova) OpenStack Compute (Nova) is a cloud computing fabric controller, which is the main part of an system. It is designed to manage and automate pools of computer resources and can work with widely available virtualization technologies, as well as and (HPC) configurations., and are available choices for technology (virtual machine monitor), together with and Linux container technology such as. It is written in and uses many external libraries such as Eventlet (for concurrent programming), Kombu (for communication), and (for database access).

Compute's architecture is designed to on standard hardware with no proprietary hardware or software requirements and provide the ability to integrate with legacy systems and third-party technologies. Due to its widespread integration into enterprise-level infrastructures, monitoring OpenStack performance in general, and Nova performance in particular, at scale has become an increasingly important issue. Monitoring end-to-end performance requires tracking metrics from Nova, Keystone, Neutron, Cinder, Swift and other services, in addition to monitoring which is used by OpenStack services for message passing.

All these services generate their own log files, which, especially in enterprise-level infrastructures, also should be monitored. Networking (Neutron) OpenStack Networking (Neutron) is a system for managing networks. OpenStack Networking ensures the network is not a bottleneck or limiting factor in a cloud deploymentand gives users self-service ability, even over network configurations. OpenStack Networking provides networking models for different applications or user groups. Standard models include flat networks or that separate servers and traffic.

Openstack Liberty Download For Machine

OpenStack Networking manages IP addresses, allowing for dedicated static IP addresses. Addresses let traffic be dynamically rerouted to any resources in the IT infrastructure, so users can redirect traffic during maintenance or in case of a failure. Users can create their own networks, control traffic, and connect servers and devices to one or more networks. Administrators can use (SDN) technologies like to support high levels of and massive scale. OpenStack networking provides an extension framework that can deploy and manage additional network services—such as (IDS), load balancing, firewalls, and virtual private networks (VPN).

Block storage (Cinder) OpenStack Block Storage (Cinder) provides persistent devices for use with OpenStack compute instances. The block storage system manages the creation, attaching and detaching of the block devices to servers. Block storage volumes are fully integrated into OpenStack Compute and the Dashboard allowing for cloud users to manage their own storage needs. In addition to local Linux server storage, it can use storage platforms including, (IBM DS8000, and ), Scality, (StoreVirtual and families), (InfiniBox). Block storage is appropriate for performance sensitive scenarios such as database storage, expandable file systems, or providing a server with access to raw block level storage.

Snapshot management provides powerful functionality for backing up data stored on block storage volumes. Snapshots can be restored or used to create a new block storage volume. Identity (Keystone) OpenStack Identity (Keystone) provides a central directory of users mapped to the OpenStack services they can access. It acts as a common authentication system across the cloud operating system and can integrate with existing backend directory services like. It supports multiple forms of authentication including standard username and password credentials, token-based systems and AWS-style (i.e. Additionally, the catalog provides a queryable list of all of the services deployed in an OpenStack cloud in a single registry.

Users and third-party tools can programmatically determine which resources they can access. Image (Glance) OpenStack Image (Glance) provides discovery, registration, and delivery services for. Stored images can be used as a template.

It can also be used to store and catalog an unlimited number of backups. The Image Service can store disk and server images in a variety of back-ends, including. The Image Service API provides a standard for querying information about disk images and lets clients stream the images to new servers.

Glance adds many enhancements to existing legacy infrastructures. For example, if integrated with VMware, Glance introduces advanced features to the vSphere family such as vMotion, high availability and dynamic resource scheduling (DRS). VMotion is the live migration of a running VM, from one physical server to another, without service interruption. Thus, it enables a dynamic and automated self-optimizing datacenter, allowing hardware maintenance for the underperforming servers without downtimes.

Other OpenStack modules that need to interact with Images, for example, must communicate with the images metadata through Glance. Also, can present information about the images, and configure a variation on an image to produce an instance. However, Glance is the only module that can add, delete, share, or duplicate images. Object storage (Swift) OpenStack Object Storage (Swift) is a scalable redundant storage system. Objects and files are written to multiple disk drives spread throughout servers in the data center, with the OpenStack software responsible for ensuring data replication and integrity across the cluster. Storage clusters scale horizontally simply by adding new servers.

Should a server or hard drive fail, OpenStack replicates its content from other active nodes to new locations in the cluster. Because OpenStack uses software logic to ensure data replication and distribution across different devices, inexpensive commodity hard drives and servers can be used. In August 2009, started the development of the precursor to OpenStack Object Storage, as a complete replacement for the Cloud Files product. The initial development team consisted of nine developers., an object storage software company, is currently the leading developer for Swift with significant contributions from HP, Red Hat, NTT, NEC, IBM and more. Dashboard (Horizon) OpenStack Dashboard (Horizon) provides administrators and users with a graphical interface to access, provision, and automate deployment of cloud-based resources. The design accommodates third party products and services, such as billing, monitoring, and additional management tools. The dashboard is also brand-able for service providers and other commercial vendors who want to make use of it.

The dashboard is one of several ways users can interact with OpenStack resources. Developers can automate access or build tools to manage resources using the native OpenStack API or the EC2 compatibility API. Orchestration (Heat) Heat is a service to multiple composite cloud applications using templates, through both an OpenStack-native REST API and a CloudFormation-compatible Query API. Workflow (Mistral) Mistral is a service that manages workflows.

User typically writes a workflow using workflow language based on YAML and uploads the workflow definition to Mistral via its REST API. Then user can start this workflow manually via the same API or configure a trigger to start the workflow on some event. Telemetry (Ceilometer) OpenStack Telemetry (Ceilometer) provides a Single Point Of Contact for billing systems, providing all the counters they need to establish customer billing, across all current and future OpenStack components. The delivery of counters is traceable and auditable, the counters must be easily extensible to support new projects, and agents doing data collections should be independent of the overall system. Database (Trove) Trove is a database-as-a-service provisioning and a non-relational engine. Elastic map reduce (Sahara) Sahara is a component to easily and rapidly provision clusters.

Users will specify several parameters like the Hadoop version number, the cluster topology type, node flavor details (defining disk space, CPU and RAM settings), and others. After a user provides all of the parameters, Sahara deploys the cluster in a few minutes. Sahara also provides means to scale a preexisting Hadoop cluster by adding and removing worker nodes on demand.

Bare metal (Ironic) Ironic is an OpenStack project that provisions bare metal machines instead of virtual machines. It was initially forked from the Nova Baremetal driver and has evolved into a separate project. It is best thought of as a bare-metal hypervisor API and a set of plugins that interact with the bare-metal hypervisors. By default, it will use and in concert to provision and turn on and off machines, but Ironic supports and can be extended with vendor-specific plugins to implement additional functionality. Messaging (Zaqar) Zaqar is a multi-tenant cloud messaging service for Web developers. The service features a fully RESTful API, which developers can use to send messages between various components of their SaaS and mobile applications by using a variety of communication patterns. Underlying this API is an efficient messaging engine designed with scalability and security in mind.

Other OpenStack components can integrate with Zaqar to surface events to end users and to communicate with guest agents that run in the 'over-cloud' layer. Shared file system (Manila) OpenStack Shared File System (Manila) provides an open API to manage shares in a vendor agnostic framework. Standard primitives include ability to create, delete, and give/deny access to a share and can be used standalone or in a variety of different network environments. Commercial storage appliances from EMC, NetApp, HP, IBM, Oracle, Quobyte, INFINIDAT and Hitachi Data Systems are supported as well as filesystem technologies such as Red Hat GlusterFS or Ceph. DNS (Designate) Designate is a multi-tenant REST API for managing DNS.

This component provides DNS as a Service and is compatible with many backend technologies, including PowerDNS and BIND. It doesn't provide a DNS service as such as its purpose is to interface with existing DNS servers to manage DNS zones on a per tenant basis. Search (Searchlight) Searchlight provides advanced and consistent search capabilities across various OpenStack cloud services. It accomplishes this by offloading user search queries from other OpenStack API servers by indexing their data into. Searchlight is being integrated into Horizon and also provides a. Key manager (Barbican) Barbican is a REST API designed for the secure storage, provisioning and management of secrets. It is aimed at being useful for all environments, including large ephemeral Clouds.

Container orchestration (Magnum) Magnum is an OpenStack API service developed by the OpenStack Containers Team making container orchestration engines such as Docker Swarm, Kubernetes, and Apache Mesos available as first class resources in OpenStack. Magnum uses Heat to orchestrate an OS image which contains Docker and Kubernetes and runs that image in either virtual machines or bare metal in a cluster configuration. Root Cause Analysis (Vitrage) Vitrage is the OpenStack RCA (Root Cause Analysis) service for organizing, analyzing and expanding OpenStack alarms & events, yielding insights regarding the root cause of problems and deducing their existence before they are directly detected. Rule-based alarm actions (Aodh) This alarming service enables the ability to trigger actions based on defined rules against metric or event data collected by Ceilometer or Gnocchi. Historical names Several OpenStack projects changed names due to trademark issues. Neutron was formerly known as Quantum.

Sahara used to be called Savanna. Designate was previously known as Moniker. Trove was formerly known as RedDwarf. Zaqar was formerly known as Marconi. Compatibility with other cloud APIs OpenStack does not strive for compatibility with other clouds' APIs. However, there is some amount of compatibility driven by various members of the OpenStack community for whom such things are important.

The EC2 API project aims to provide compatibility with. The GCE API project aims to provide compatibility with Governance OpenStack is governed by a non-profit foundation and its board of directors, a technical committee, and a user committee. The board of directors is made up of eight members from each of the eight platinum sponsors, eight members from the 24 defined maximum allowed Gold sponsors, and eight members elected by the Foundation individual members.

Appliances An OpenStack Appliance is the name given to software that can support the OpenStack on either physical devices such as or or a combination of the two. Typically a is a set of software capabilities that can function without an operating system. Thus, they must contain enough of the essential underlying operating system components to work.

Therefore, a strict definition might be: an application that is designed to offer OpenStack capability without the necessity of an underlying operating system. However, applying this strict definition may not be helpful, as there is not really a clear distinction between an appliance and a.

It could be argued that the term appliance is something of a misnomer because OpenStack itself is referred to as a cloud operating system so using the term OpenStack appliance could be a misnomer if one is being pedantic. If we look at the range of Appliances and Distributions one could make the distinction that distributions are those toolsets which attempt to provide a wide coverage of the OpenStack project scope, whereas an Appliance will have a more narrow focus, concentrating on fewer projects.

Vendors have been heavily involved in OpenStack since its inception, and have since developed and are marketing a wide range of appliances, applications and distributions. Vendors A large number of vendors offer OpenStack solutions, meaning that an organization wishing to deploy the technology has a complex task in selecting the vendor offer that best matches its business requirements. Barb Darrow offered this over view in Fortune on May 27 2015, pointing out that there may be some consolidation in the market that will clarify things. There are other aspects that people need to consider, for example, the real costs involved. How much of the actual OpenStack platform is offered? Some vendors will make an offer which encompasses most of the OpenStack projects; others will only offer certain components.

Please refer to the table below for details. Other considerations: to what extent has a vendor injected proprietary code to manage a lack of maturity in an OpenStack component? And to what extent does proprietary code mean vendor lock-in? The most authoritative information on vendor products is at the OpenStack Foundation website. Challenges to implementation Openstack is a complex entity, and adopters face a range of challenges when trying to implement OpenStack in an organisation. For many organisations trying to implement their own projects, a key issue is the lack of skills available. In an article on The New Stack, Atul JHA succinctly identifies five challenges any organization wishing to deploy OpenStack will face.

Installation challenges OpenStack is a suite of projects rather than a single product, and because each of the various applications needs to be configured to suit the user's requirements, installation is complex and requires a range of complementary skill-sets for an optimum set-up. One obvious solution would be to take a complete vendor supplied package containing hardware and software, although due diligence is essential. Documentation This is more a function of the nature of documentation with open source products than OpenStack per se, but with more than 25 projects, managing document quality is always going to be challenging. Upgrading OpenStack One of the main objectives of using cloud type infrastructure is that it offers its users not only high reliability but also high availability, something that public cloud suppliers will offer in Service Level Agreements.

Such is the nature of OpenStack, due to its multi-project development approach, is that the complexity involved in synchronising the different projects during an upgrade implementation may mean that downtime is an unavoidable consequence. Long term support It’s quite common for a business to keep using an earlier release of software for some time after it has been upgraded. The reasons for this are pretty obvious and referred to above. However, there is little incentive for developers in an open source project to provide support for superseded code.

In addition, OpenStack itself has formally discontinued support for some old releases. Given the above challenges the most appropriate route for an organization wishing to implement OpenStack would be to go with a vendor, and source an OpenStack appliance or distribution. Users OpenStack has a wide variety of users, from a number of different sectors. Notable users include.

– joined OpenStack in January 2012. Now PaddyPower Betfair has a private cloud which will support its entire productions stack - named 'i2'. has a private cloud to cater to in house employees' requirements. has created a 'Business Marketplace', whose functionality is based on OpenStack and operated by.

offers public. British tax collectors., which combines software and cloud services into a unified set of packages and under a single unified architecture. Retrieved 17 September 2017. Retrieved 29 November 2013. 19 September 2012. Retrieved 7 January 2013.

Retrieved 7 January 2013. Retrieved 7 January 2013. 27 July 2011. Retrieved 23 October 2012. Retrieved 23 October 2012. Retrieved 23 October 2012.

10 December 2013. Retrieved 11 December 2013. 3 March 2014. Retrieved 5 March 2014.

3 March 2014. Retrieved 5 March 2014. Sean Michael Kerner. Enterprise Networking Planet. Hamilton, David. Retrieved 2 April 2015. 16 July 2015.

Retrieved 20 July 2015. 16 March 2016.

Alpha channel remover for mac. Retrieved 10 February 2017. Curry, Jim (19 July 2010). Retrieved 22 January 2017.

Docs Openstack. Openstack Foundation. Retrieved 17 September 2015. Openstack Foundation. Retrieved 17 September 2015. Eskey, Megan.

FARA on Steroids. OpenNASA v2.0 cloud architecture. NASA Nebula Cloud Architecture. Vaughan, Steven J. (10 May 2011).

Retrieved 23 October 2012. Vaughan, Steven J. (3 February 2011). Retrieved 11 January 2014.

Thomas Goirand. 6 February 2013. Retrieved 29 November 2013. Thomas Goirand. 17 October 2013. Retrieved 29 November 2013. SUSE press release.

26 October 2011. Retrieved 9 August 2016.

SUSE press release. 29 August 2012. Retrieved 9 August 2016. Linux Weekly News. 15 August 2012. Retrieved 26 August 2013. Red Hat Press Release.

12 June 2013. Retrieved 11 January 2014. Openstack Organisation. Openstack Foundation.

Retrieved 17 September 2015. Babcock, Chris (18 June 2012). Information Week. Retrieved 17 September 2012. 29 July 2013. Retrieved 14 March 2014. Retrieved 18 June 2015.

10 December 2013. 29 April 2014. 31 July 2014. 24 September 2014.

(Press release). Retrieved 7 May 2014. 'Interop 2014: Avaya to showcase Automated Campus part of SDN initiative'. Info Tech Lead. 26 March 2014. Missing or empty url= ; access-date= requires url=.

Tech Field Day. Retrieved 25 June 2014.

14 April 2015. Archived from on 12 April 2015. Retrieved 21 April 2015. OpenStack Foundation. Retrieved 7 January 2013. OpenStack Foundation.

Retrieved 7 January 2013. Retrieved 2018-05-11. Retrieved 2018-05-11. Retrieved 2018-09-24. Retrieved 2017-09-12. Retrieved 17 April 2014. Retrieved 31 March 2014.

Retrieved 29 November 2013. Retrieved 29 November 2013. Retrieved 17 October 2016. Retrieved 17 October 2016. Dynatrace blog – monitoring redefined. Retrieved 2017-09-12.

Retrieved 10 August 2014. Retrieved 10 August 2014. Retrieved 10 August 2014.

Retrieved 6 May 2014. Retrieved 28 June 2016. Retrieved 6 May 2014. Retrieved 24 September 2014.

Retrieved 24 September 2014. Retrieved 24 September 2014.

Retrieved 24 September 2014. OpenStack Wiki. Retrieved 1 June 2015. OpenStack Wiki. Retrieved 1 June 2015.

Retrieved 20 February 2016. Retrieved 20 February 2016. Retrieved 20 February 2016.

OpenStack Wiki. Retrieved 1 June 2015. OpenStack Wiki. Retrieved 3 October 2017. OpenStack Documentation. Retrieved 3 October 2017.

McClain, Mark (19 June 2013). Openstack-dev mailing list.

Retrieved 16 July 2013. Lukjanov, Sergey (7 March 2014).

Openstack-dev mailing list. Retrieved 8 May 2016. Mac Innes, Kiall (9 March 2013). Openstack-dev mailing list. Retrieved 8 May 2016. Blair, James (12 June 2013). Openstack-dev mailing list.

Retrieved 8 May 2016. Retrieved 24 September 2014. Retrieved 24 September 2014. OpenStack Foundation. Retrieved 15 January 2013. Openstack Foundation.

Retrieved 17 September 2015. Retrieved 17 September 2015. Datta, Alana (1 September 2009).

Retrieved 17 September 2015. OpenStack Foundation. Retrieved 21 September 2015.

Allen, Scott (19 May 2015). Intel Communities. Retrieved 17 September 2015. Darrow, Barb (7 May 2015). Retrieved 17 September 2015. Finnegan, Matthew (1 May 2015).

Retrieved 17 September 2015. Clark, Jack (13 May 2014). The Register. The Register. Retrieved 17 September 2015. Donnelly, Caroline (3 March 2015). Computer Weekly.

Retrieved 17 September 2015. Openstack Foundation. Tsidulko, Joseph (6 August 2015). The Channel Company. Retrieved 17 September 2015. Jha, Atul (December 2011).

The New Stack. Retrieved 17 September 2015. Laube, David (12 January 2015). Retrieved 17 September 2015. SVERDLIK, Yevgeniy (April 1, 2015). Data Center Knowledge. Retrieved 17 September 2015.

Lester, Andy (10 January 2013). SmartBear Software. Retrieved 17 September 2015. Arcitura Education Inc.

Retrieved 21 September 2015. Baset, Salman. Retrieved 21 September 2015. Darrow, Barb (20 December 2013). Knowingly Inc.

Retrieved 21 September 2015. Openstack Foundation. Retrieved 17 September 2015. Retrieved 29 November 2013. Retrieved 23 October 2012. Retrieved 30 April 2015.

Retrieved 8 January 2016. Retrieved 10 August 2017.

Retrieved 5 November 2015. Retrieved 10 November 2015. (German).

Retrieved 17 November 2014. 28 February 2012. Retrieved 2 November 2017. Craft, Valentina (12 June 2013). Retrieved 21 April 2016. 29 December 2013. Retrieved 9 April 2014.

Retrieved 12 July 2013. Retrieved 9 April 2014. 8 December 2015. Retrieved 8 December 2015.

Cowan, Paris (30 August 2013). Retrieved 13 February 2014. Retrieved 13 February 2014. 19 January 2018. Network World. 6 April 2016.

Retrieved 11 September 2014. Retrieved 9 April 2014. Bruekner, Rich (13 May 2014). Retrieved 10 March 2016. Chase, Nick (29 September 2014). Mirantis, Inc.

Retrieved 26 February 2016. Oracle OpenStack for Oracle Linux, or O3L, is now available, enabling customers to control both Oracle Linux and Oracle VM using OpenStack. It also, however, comes with the announcement of a 'mutual cooperation and support' agreement with Canonical, seen as a direct shot at Red Hat. Retrieved 29 June 2016.

VMware Integrated OpenStack is a full OpenStack distribution that enables IT administrators to foster developer innovation by deploying and managing production grade OpenStack quickly and easily on top of their VMware infrastructure. See more at:. Retrieved 23 October 2012. Archived from (PDF) on 13 May 2013. Retrieved 23 October 2012. 20 January 2011. Archived from on 2 November 2012.

Retrieved 23 October 2012. 12 April 2011.

Retrieved 23 October 2012. 6 September 2011. Retrieved 23 October 2012. 7 March 2012. Retrieved 23 October 2012. Retrieved 23 October 2012.

Retrieved 4 April 2013. Retrieved 19 June 2013. Retrieved 17 April 2014. Retrieved 23 September 2014. Retrieved 23 September 2014. Retrieved 20 February 2016. Retrieved 20 February 2016.

Retrieved 8 October 2016. Retrieved 22 February 2017. Retrieved 17 September 2017. Retrieved 16 April 2018. External links Wikimedia Commons has media related to.