Activity Not Available
I Use This!


Analyzed about 1 month ago. based on code collected about 1 month ago.
Posted 2 days ago by Dave Van Everen
The post Let’s meet in Barcelona at the OpenStack Summit! appeared first on Mirantis | The Pure Play OpenStack Company. As we count down the days to the OpenStack Summit in Barcelona on October 24-28, we’re getting ready to share memorable ... [More] experiences, knowledge, and fun! Come to booth C27 to see what we’ve built with OpenStack, and join in an “Easter Egg Hunt” that will test your observational skills and knowledge of OpenStack, Containers, and […] The post Let’s meet in Barcelona at the OpenStack Summit! appeared first on Mirantis | The Pure Play OpenStack Company. [Less]
Posted 2 days ago by Openstack Security Project
OpenStack is one of the largest Python projects, both in code size and number of contributors. Like any development language, Python has a set of best (and worst) security practices that developers should be aware of to avoid common security ... [More] pitfalls. One mission of the OpenStack Security Project is to help developers write Python code as securely and easily as possible, so we created two resources to help. Secure Development Guidelines The Secure Development Guidelines were created with the goal to make it quick and easy for a developer to learn: - What is the best practice - An example of the incorrect (insecure!) way of accomplishing a task - An example of the correct way of accomplishing a task - Consequences for not following best practices - Links for further Reference As developers ourselves we’re guilty of more than the occasional copy-paste. The Correct section of the Secure Development Guidelines are a perfect source to jump in and get the best practice code snippet you need. Bandit Bandit was built to find common insecure coding practices in Python code. Developed for the OpenStack community by the OSSP, it is the best Python static analysis tool available (in our biased opinion). Like all OSSP resources and tools, Bandit is open source and we encourage people to use it, extend it, and provide feedback. If you’re new to Bandit a good way to get started is by watching this: Also check out our wiki. If you have any questions please contact us on the OpenStack Developer Mailing list (using the [Security] tag), or visit us on IRC in #openstack-security on Freenode. [Less]
Posted 2 days ago by Luke Odom
This is post No. 2 in a series of posts about how DreamHost builds its Cloud products. Written by Luke Odom straight from data center operations.  In this post, we are going to be looking at what processor we are using in the new DreamCompute ... [More] cluster, and how we picked it! A processor is one […] The post How DreamHost Builds Its Cloud: Selecting Microprocessors appeared first on Welcome to the Official DreamHost Blog. [Less]
Posted 2 days ago by Carlos Camacho
Posted 2 days ago by Rob LeFebvre
Collaboration is key with these two powerhouse open-source platforms. The post Why OpenStack and Kubernetes are better together appeared first on OpenStack Superuser.
Posted 2 days ago by John Engates
Apple made big news earlier this year when it moved its iCloud service to the Google Cloud Platform while also continuing to make heavy use of AWS and Azure. But according to Larry Dignan, Editor-in-Chief at ZDNet, the real story is that this move in ... [More] no way makes them unique: “Let’s replace Apple with any The post Navigating the Multi-Cloud Maze appeared first on The Official Rackspace Blog. [Less]
Posted 2 days ago by Isaac Gonzalez
A new book offers common OpenStack Deployments with real-world examples for systems administrators and engineers. The post Considering OpenStack? A new book shows you how to get started appeared first on OpenStack Superuser.
Posted 2 days ago by Alex Campanelli
The Tesora team is heading to the OpenStack Summit in Barcelona next month. From October 25-28, you can find us in the marketplace at Booth B33, as well as leading several presentations on Database as a Service. If you’re a fan of OpenStack Trove ... [More] , join us for these talks: Tuesday, 10/25: 11:25 am- 12:05 pm […] The post Join Us in Barcelona Next Month! appeared first on Tesora. [Less]
Posted 2 days ago by Mark_Smith
According to the famous quote-master Yogi Berra, “nostalgia ain’t what it used to be”.  While that may be true, the open source community couldn’t resist indulging in some well-earned nostalgia recently.  Having just passed major milestones of 25 ... [More] years for Linux and 6 years of OpenStack, we’ve had the chance to look back at the … +read more The post OpenStack Past, Present and Future appeared first on SUSE Blog. Mark_Smith [Less]
Posted 2 days ago by Chris Dent
Despite its name, the Technical Committee has become the part of the OpenStack contributor community that enshrines, defines, and -- in some rare cases -- enforces what it means to be "OpenStack". Meanwhile, the community has seen a great deal of ... [More] growth and change. Some of these changes have led to progress and clarity, others have left people confused about how they can best make a contribution and what constraints their contributions must meet (for example, do we all know what it means to be an "official" project?). Much of the confusion, I think, can be traced to two things: Information is not always clear nor clearly available, despite valiant efforts to maintain a transparent environment for the discussion of policy and process. There is more that can be done to improve engagement and communication. Maybe the TC needs release notes? Agreements are made without the full meaning and implications of those agreements being collectively shared. Most involved think they agree, but there is limited shared understanding, so there is limited effective collaboration. We see this, for example, in the ongoing discussions on "What is OpenStack?". Agreement is claimed without actually existing. We can fix this, but we need a TC that has a diversity of ideas and experiences. Other candidates will have dramatically different opinions from me. This is good because we must rigorously and vigorously question the status quo and our assumptions. Not to tear things down, but to ensure our ideas are based on present day truths and clear visions of the future. And we must do this, always, where it can be seen and joined and later discovered; gerrit and IRC are not enough. To have legitimate representation on the Technical Committee we must have voices that bring new ideas, are well informed about history, that protect the needs of existing users and developers, encourage new users and developers, that want to know how, that want to know why. No single person can speak with all these voices. Several people have encouraged me to run for the TC, wanting my willingness to ask questions, to challenge the status quo and to drive discourse. What I want is to use my voice to bring about frequent and positive reevaluation. We have a lot of challenges ahead. We want to remain a pleasant, progressive and relevant place to participate. That will require discovering ways to build bridges with other communities and within our own. We need to make greater use of technologies which were not invented here and be more willing to think about the future users, developers and use cases we don't yet have (as there will always be more of those). We need to keep looking and pushing forward. To that end I'm nominating myself to be a member of the Technical Committee. If you have specific questions about my goals, my background or anything else, please feel free to ask. I'm on IRC as cdent or send some email. Thank you for your consideration. [Less]