On the first part of this series I talked about, when I started working for Fiercely, it became important to improve the performance of a vagrant powered environment, on OSX, and how we came across xhyve.
In this post, the second of the series, will be in the form of a tutorial (kind of), on how to run a CentOS 7 on OS X using xhyve. This will mostly put together a series of posts on the subject (see references) and add the minimal configuration to make a Virtual Machine (VM) vagrant ready.
From the author’s description ”xhyve, a lightweight OS X virtualization solution” and you can find the project on github. …
This solution was born after an industrial partner identified a special and focused need. They needed to get information from their production lines in near-real time, through messaging. They already had a working solution, based on SMS, but this solution would not scale within their budget. Since they wanted to increase the monitored events and therefore, the number of messages, the communication costs would grow exponentially. So, in order to fulfill this need, they looked at how to take advantage of internet-based text messaging solutions. Also, the industrial partner had a very short timeframe to put this solution in place.
Using this starting point, we presented a continuous integration and delivery approach for delivering them the solution, making possible for them to define their priorities. In order to make sure they had a predictable and adaptable solution, we also decided to use Docker containers for the main components. By using this, we could deliver the solution in different hardware platforms they might have (e.g. …
In one guest blog post that we wrote for SkeltonThatcher blog (https://skeltonthatcher.com/blog/dealing-continuous-delivery-anti-patterns/) , we started talking superficially about a major negative influencer on delivery perfomance. We discussed how the business and technical staff having (de-)evolved into completely siloed functions, communicating almost always via email, specification documents or specification tools.
Now, we would like to specifically address this issue.
One might see this problem as related to Business analysts’ responsibilities, to Product Owner way of working or any other role the team might have. However, the point in this discussion is that we don’t care about the role.
What we have found important is that the team, as a whole, needs to clearly understand why and what is important, taking responsibility and addressing feature delivery as the mean to an end: to achieve a specific business value. In order to achieve this, the team needs to be able to answer some…
All of our team members individually believe in the power of communities. Luckily, we participated in some interesting ones. Therefore, it was almost natural for us to sponsor a very active community that spreads the word on some of our most important concepts.
This community, the Devops Lisbon Meetup has already over 500 members, and we are very proud to help them grow even more.
I have recently joined Fiercely and an interesting problem arose when I had to set up my environment, there is no way to run a linux CentOS box in a lightweight virtualization provider other than Docker on OSX.
At Fiercely, we are intensive users of Vagrant, as some of our clients have applications deployed on Windows connected to applications deployed on Linux, and vice-versa. As such, in order to be able to help them, we must be able to mimic this ecosystem on our machines. I know what you’re thinking “Just use Docker already…” and, trust me, we would but, some client systems are just not there yet. …
During these 2 days, the team had the chance to meet with several different vendors in the fair and also attend some interesting talks in the conference.
At the fair, we would like to point out the very nice talk we had with the guys from Puppet and Chef, two major references in the automation and provisioning domain. It’s interesting to find out that, although with different implementation approaches, both are working towards a more robust way of delivering software based on provisioning automation.
From the talks, of course we followed with higher interest the DevOps track, which was also the one with greater attendance. We would like to mention a very good talk from Matthew Skelton (slides here) on Continuous Delivery anti-patterns. Many of the suggested patterns are aligned with solutions we have effectively applied when we find these (surprisingly recurring) anti-patterns. …
Like any other startup, we had to worry about putting up a few things first, like clients, projects, and team.
Now, we finally got some time to start writing some text. We’ll be using this space to share our thoughts, achievements, problems and anything else.
At Fiercely, we are very much focused on improving our clients’ software development teams performance by using solid engineering techniques.
So, stay tuned if you are also interested in this.