Today I am going to write a quick post about a great show for developers that is coming up - DevNation. It is a show for developers put together by developers at Red Hat. It will be held in San Francisco from April 13-17 this year. The bonus is that since Red Hat has so many different developer platforms and languages we support - you get your pick of topics to learn about.
OpenShift Origin didn't get on GitHub's top 5 list of pull requests for 2013 by accident. It happened because developers and operations alike understand how important the idea of Platform-as-a-Service really is. OpenShift Origin Community Manager, Diane Mueller said it best with her recent blog post: PaaS is Eating the World.
With all of this buzz around GitHub and our tremendous development activity over the past year, I figured now would be a good time to explain how you can get involved with the OpenShift community.
Controlling application sprawl within your organization can be a daunting task - especially with today's constantly-evolving and ever-increasing proliferation of languages, frameworks, services, and data stores. IT Managers and operation teams must deal with the day-to-day realities and challenges of IT, as well as meet developers' demands for access to tooling that will help them produce, delivering reliable results to customers.
The rise of the Public PaaS (OpenShift Online included) has granted developers access to new levels of freedom when selecting a language, framework, and set of services, or data stores that are a 'best fit' for the task at hand. Sometimes, it can seem like a never-ending battle.
In the past, application sprawl was managed by enterprises by "standardizing" or "locking down" the range of languages and technologies that developers were allowed to utilize.
OpenShift Online releases come roughly every 3 weeks and are chock-full of great features that enable users to onboard and manage their production-grade web applications and mobile application back-ends. With the completion of each upgrade, a release blog is written to summarize the new user-facing features.
Welcome to the OpenShift Developer Spotlight where we get to know the members of the OpenShift community a little better and show off their skills as developers.
While the world's been "going for the gold," we've been busy pushing new code. With this latest release come the usual amount of new features and a better Openshift Online experience.
We've Shifted our forums over to Stackoverflow
Our community of users and developers is always growing.
Today we're proud to announce the open sourcing of our montioring scripts. The OpenShift Online Operations Team has published the OpenShift-Zabbix repository containing the monitoring scripts to monitor an OpenShift installation.
We use these scripts to monitor OpenShift Online environment using Zabbix. They are aimed at giving OpenShift Enterprise and OpenShift Origin users a good starting point for monitoring their OpenShift deployments as well.
The OpenShift-Zabbix repository is structured in the standard Puppet module format. We don't expect every consumer to also use Puppet in their infrastructure.
I am pleased to announce that I have tagged the backup cartridge I have been working on as 1.0. It is a simple web application that will allow you to take snapshots of your other applications, either once off or on a scheduled interval.
- Schedule backups to run daily, weekly, or monthly
- Take a snapshot of the gear when it is stopped/idled
- Restore snapshots with the click of a button
- If the backup cartridge is stopped, any scheduled backups will not be ran
- This mostly applies to free teir users on OpenShift Online. One off backups will still work just fine but do not expect to rely on scheduled jobs.
- Scaled gears are untested. In theory they should just work
- Disk space is limited.