OpenStack

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]

Updates: Nova placement/resource provider work [4] New release-announce list and other changes to openstack-announce [5] Formal Discussion of Documenting Upgrades[6] Stewardship Working Group description/update [7] OpenStack Liberty has reached EOL ... [More] [8] Switching test jobs from Ubuntu Trusty to Xenial on the gate is happening on December 6th [9] A Continuously Changing Environment: We have core... Read more » [Less]

Data storage growth is both a reality and a burden for today’s enterprises. With the move to digital, big data and, data intensive workloads, enterprises are storing an increasing amount of data, growing 30-40 percent per year, according to Vanson Bourne LTD. Much of this growth comes from applications running on cloud platforms such as […]

When it comes to communities, a system is the set of processes you put in place to allow for humans to be amazing. It's the means to empower these humans to contribute to your community, learn from it and grow with it. These systems are essential for ... [More] your community to exist. Your community is a system in itself and it functions through the processes that have been created along the way. These processes exist even if you're not aware they do. The processes that help your community function are not some kind of magic tunnel through which things happen automatically. These are processes created and tailored for your community. There are many things that can be shared across different communities but there are others that are simply specific to yours. The way you merge code, the means through which you communicate in your community, the standards you put in place. These are all processes that allow your community to cope with growth and chaos. These processes are all meant to be created, evolve and sometimes die. If you want your community to survive change, you must change your community therefore you must change your processes. There's no secret recipe for managing these processes, though. One thing to always keep in mind is that the humans that interact with these processes are more important than the processes themselves. If the way you review code is too complex for most of the humans that are doing reviews, change it. If the way you define new processes doesn't allow other humans to actively participate, change it. If the way you allow for contributions to be submitted ends up frustrating your contributors, change it. Your community is made by humans and the sooner you acknowledge that, the sooner you'll adapt your processes to better empower these humans. Remember that humans react to emotions (you can read more here) but they act based on their cultures. Culture has been defined in many ways. Some definitions involve long explanations about society, evolution and human interaction. When it comes to communities a, perhaps oversimplified, way to define culture is that it's the way humans in the community actually do things. I heard this definition at Zingtrain in June 2016 and it stuck with me. Not only it makes sense on paper but it's also true in reality. We spend a huge deal of time defining new processes in OpenStack that would help the community evolve and adapt itself and we see over and over how many of these processes change as soon as other humans start interacting with them. Sometimes this interaction ends up in processes being "officially" changed and many times they are left as they are so people can use them the way it works best. In other words, the processes in your community will be bent by the cultures in your community more often than not and this is fine. You want this to happen. You want your community to adapt itself to the cultures that it embraces. You want your community to embrace more cultures and to allow for new cultures to be created within the community itself. Different cultures have different ways to solve problems and there's lots your community can learn from this. Your community must be flexible for it to be able to adapt itself and tolerate the bending of its processes caused by the interaction with other cultures. If the processes in your community can't be bent a bit, then some cultures won't be able to interact with them and this will, of course, affect your community. For humans from different cultures (even the same culture, really) to be able to interact with each other, they must be tolerant to variance. Putting the tolerance to variance at the bases of your community will set the principle that humans in your community will interact based on. There must be balance, though. Being either too tolerant or too intolerant won't help your community. You can't make everyone happy but you definitely must make enough humans happy. Eventually it will come down to how good your community is at allowing humans to interact with each other and I believe a good summary of this post could be: You must tolerate variance in your community, to empower humans, hopefully from any culture, to be amazing. If you liked this post, you may also like: On communities: Emotions matter On communities: Sometimes it's better to over-communicate If you liked this post, you may be interested in the keynote I gave at Pycon South Africa. Keeping up with the pace of a fast growing community without dying [Less]