OpenStack Nova

Madhura Maskasky introduces OpenStack Omni, a set of drivers to manage and control resources on AWS. The post Manage resources on AWS with OpenStack Omni appeared first on OpenStack Superuser.

Increased investment, adoption signal strength of the local community. The post China puts money where the cloud is, ramps up OpenStack adoption appeared first on OpenStack Superuser.

19 commits, 59 changed files, 2,404 additions and 588 deletions… and more than a month’s on and off work. 0.10 is out ! Where to get it ? Get started easily by installing and configuring ARA. I’m excited to tell you about this new release ! Here’s a ... [More] few highlights ! An improved web application browsing experience A lot of work has gone into the browsing experience: less clicks, more information, faster. I am by no means a professional frontend developer and I would definitely love help on this front but I think things are definitely starting to look good ! I’ve added updated previews to the documentation: In screenshots In video where we I showcase some playbook runs by the OpenStack-Ansible project. It’s awesome to see how much the interface has improved over time. Curious ? Look at the Alpha and Beta video previews to see how far the project has come ! Two new Ansible modules This new release features two new Ansible modules, ara_record and ara_read. These allow you to respectively write and read persistent data that is made available throughout your playbook run and in the web interface. For example: --- - name: Test playbook hosts: localhost tasks: - name: Get git version of playbooks command: git rev-parse HEAD register: git_version - name: Record git version ara_record: key: "git_version" value: "{{ git_version.stdout }}" That would make the git_version key/value available in the web interface and on the CLI. And you can record different kind of data, too, see: --- - ara_record: key: "{{ item.key }}" value: "{{ item.value }}" type: "{{ item.type }}" with_items: - { key: "log", value: "error", type: "text" } - { key: "website", value: "http://domain.tld", type: "url" } - { key: "data", value: '{ "key": "value" }', type: "json" } Setting a type will make it so it’s displayed accordingly in the interface. More types will eventually be made available ! Improved unit and integration testing coverage In order to make sure ARA works well — and keeps working well — we need to have a good amount of unit and integration testing. This coverage was improved since the previous release and additionnally, we now test against different versions of Ansible on both CentOS and Ubuntu. Database schema finally declared stable Was ARA unstable before ? Not really. However, at the rapid pace of development we were having with the project, we decided to avoid managing SQL migrations to avoid unnecessary overhead as the database schema was moving a lot. I feel the database is fairly fleshed out at this point at any new modifications will be handled automatically when running ARA. Any version of ARA >= 0.9.0 is considered a stable and managed database schema. This is great, let’s make it better ! The feedback around ARA has been awesome, keep it coming ! A lot of the improvements that are part of this release is directly from ideas and comments provided by users. If you want to come chat, learn or discuss about ARA, you’ll find us on #ara on IRC in the freenode server ! [Less]

Today, we have some big news at AppFormix. Juniper Networks announced today its intent to acquire AppFormix. This is great news for our team, our customers and our technology.

Ever since I’ve been involved with OpenStack people have been complaining that upstream is hard. The number one complaint is that it takes forever to get your patches merged. I thought I’d take a look at some data and attempt to visualize it. I wrote some code that accepts an OpenStack project and a list […]

Every month, our HX201 Cloud Fundamentals for OpenStack course gets a refresh. Usually, those are small, incremental changes, but this December there's a bigger update. OpenStack Newton Firstly, we've updated the course from OpenStack Mitaka to ... [More] OpenStack Newton, the latest OpenStack release that dropped just a few weeks back. This means that you now get to deploy an OpenStack cluster, live and fully interactively as before — except you are now deploying the very latest OpenStack release. Ubuntu-branded OpenStack Dashboard (Horizon) running on OpenStack Newton (screenshot taken from HX201 course) Juju 2.0 As always, the course comes in two flavors: one with OpenStack managed with OpenStack-Ansible, and another with Juju. And as far as Juju is concerned, here's the other big change: the entire course now runs based on Juju 2.0. This also means you get to deploy your OpenStack services into LXD containers, have a new and improved Juju GUI at your disposal, and are able to take advantage of the much more intuitive CLI. Juju 2.0 GUI with fully deployed OpenStack (screenshot taken from HX201 course) Ubuntu 16.04 LTS And finally, of course, this refresh means that we've also updated to the latest Ubuntu LTS release (16.04 Xenial Xerus). This goes for both the Ansible and the Juju 2.0 course flavor. Get it while it's hot! Want to get some new knowledge into your system before the year is over? Now is your chance. HX201 is available for purchase from our web site, and you can get cracking any time. [Less]

Let's look at a few highlights from OpenStack's 2016 Newton release.

Container schedulers promise to reduce operational complexity and improve interoperability, but there's much work left to be done says Rob Hirschfeld. The post What do you think of a joint Kubernetes OpenStack environment? appeared first on OpenStack Superuser.

At the end of October I attended the OpenStack Ocata Summit in beautiful Barcelona. My participation in this was a bittersweet one for me. It was the first summit following the release of our Common OpenStack Deployments book and OpenStack Infrastructure tooling was featured in a short keynote on Wednesday morning, making for quite the […]

There are many reasons you will want to package your code as a plugin. The most important reason is that it ensures the longevity and reliability of your code. Things are constantly changing in Horizon, but as long as your adhere to the plugin ... [More] architecture, we guarantee that our releases will not break your plugin. The post Writing a Horizon Plugin appeared first on IBM OpenTech. [Less]