We are happy to announce that AnsibleFest will be returning to San Francisco this November. After a sell-out AnsibleFest in New York City, we have moved the West Coast event to an even larger location.
If you are new to Ansible, AnsibleFest is a day-long conference bringing together hundreds of Ansible users, developers and industry partners to share best-practices, case studies and Ansible news. AnsibleFest is for anyone who is passionate (or becoming passionate) about Ansible.
Attendees include DevOps engineers, operations engineers, open source fans, systems engineers, system administrators, operations staff, release engineers, DBAs, network engineers and security professionals.
Again, we are offering Super Early Bird pricing for just $275 a ticket through August 31st. Don't miss out as we are only offering a limited number of Super Early Bird tickets at this time.
We are also accepting speaker applications here.
Here is a sample of what to expect at AnsibleFest San Francisco 2015.
See all of the presentations here.
This is not a generic “Postgres vs. MongoDB” performance post. This post details the process of comparing Postgres vs. MongoDB with a particular use case in mind, System Tracking.
Postgres is a candidate database since it is already in use by Tower. MongoDB is the other database considered for an in depth analysis for many reasons including: (1) document store of the JSON structure, (2) arbitrary structure query support, (3) and the ability to run on a single machine and later scale.
Comparing the two databases begins with identifying our System Tracking requirements. What is System Tracking?
For Tower, System Tracking is time based snapshots of machine facts. Facts are key value pairs of system state. The inspiration comes from the open source Ansible. Ansible facts will be supported in System Tracking along with 3 other fact types: packages (i.e. rpm or apt-get), services (i.e. mongodb, apache2), and files (i.e. /var/log/message). We support these 3 facts as fact modules. We also want to allow for customer built modules. Facts generated by the 4 core modules plus user created modules would be stored in Tower’s System Tracking database; allowing customers to take advantage Continue reading
Knowing the members of our Ansible community is important to us, and we want you to get to know the members of our team in the Ansible office. Stay tuned to the blog to learn more about the people who are helping to bring Ansible to life.
This week we're happy to introduce you to Tim Cramer, VP of Engineering at Ansible. Tim brings over 20 years of enterprise software experience to Ansible. He was previously at HP where he was responsible for the overall delivery of Helion Eucalyptus Cloud, managing global teams of engineering, support and IT. He also worked as an executive at Dell, Eucalyptus, and Sun Microsystems, and as an engineer at Sun and Supercomputer Systems Inc.
What’s your role at Ansible?
Running the development and release of Ansible Tower and managing the Ansible open source team and community efforts
Scaling the engineering team and increasing the ability to release products more often and with higher quality
Overseeing partner engineering integrations that benefit Ansible customers and users; for example, working on enhancing Windows, VMware, OpenStack, and AWS functionality
Understanding and prioritizing the features for Tower releases
What’s your management philosophy?
My philosophy is not unlike the great Continue reading
While prior versions of the Ansible Tower documentation focused on a single PDF, we've gone in a different direction for this release. You will still have all of the great content available from earlier releases, but in a documentation set comprised of guides focused on getting you going, installation and reference, administration, and more. I have to say that all of the outstanding documentation that was created for prior versions gave me a strong foundation to work with for this release and I'm grateful for the hard work put in before I joined the Ansible team.
With Ansible Tower 2.2, we are ensuring that access to HTML as well as PDF versions of the Tower documents are easily available from the docs website. Our Ansible Tower HTML documents also look and feel more similar to the Ansible documentation available online that you've come to know and love. And, they've been indexed to help you find the information you need as quickly as possible.
First, we're introducing Ansible Tower to new users with our Quick Installation and Quick Setup Guides. These manuals are geared toward getting Ansible Tower installed and setup to the point of running a simple playbook. They Continue reading
We’re happy to announce that Ansible Tower 2.2 is now available.
Ansible Tower is the console and service that builds on the solid foundation of Ansible’s simple automation to bring the control, security, and delegation you need to spread automation across your IT infrastructure. We’ve worked hard to update Tower to bring new capabilities to our users. I’ve talked about these some when I discussed how Tower 2.2 was coming soon - now I’d like to go into a little more detail.
We’ve talked to many of our customers who use Tower on an everyday basis. And the continuing refrain is:
“Foreground the stuff we need every day. Background what we don’t.”
We’ve started that process with Tower 2.2. First, you’ll notice the changes on the dashboard, where we’ve removed extraneous graphs so you can concentrate on the important information - are your hosts OK, and are your jobs succeeding. Plus, you’ll see lists of both recent completed jobs, and recently used playbooks.
We’ve also added sparklines to the display of job templates so that wherever you’re seeing your job templates, you have an easy visual display of how that job Continue reading
Welcome to Technology Short Take #52, the latest collection of news, links, and articles from around the web on data center technologies.