Archive for the ‘Dojo’ Category

Introducing Tyro [Powered by Dell EMC Dojo]! Your team's way of embarking on the Dojo Path to Enlightenment

Your team's way of embarking on the Dojo Path to Enlightenment

Emily Kaiser

Emily Kaiser

Head of Marketing @DellEMCDojo #CloudFoundry #OpenSource #TheWay #LeanPractices #DevOps #Empathy

The Way is spreading like wildfire and we could not be happier about it. The methodology, in particular, has unprecedented buy-in from all levels. We get questions multiple times a day about how and when teams can pair with us. At first we were trying to accommodate all requests, and to do so by reiterating that it was an all or nothing sort of deal. We found that not only was this impossible with time and resource constraints on our end, it was proving to be impossible for those interested to get in the door. This defeats the entire evangelization portion of our two-fold mission. So, as is common practice, we went back to the drawing board and created a pivot.

It is with great pride and excitement that we introduce to you the Dojo Path to Enlightenment, a step by step (or belt by belt) program that outlines for you and your team EXACTLY how to adopt The Way. This four-belt program will lead your team to certified Dojo status (i.e. enlightenment) with the intermediary step of becoming a Tyro. Through ‘customer’ discovery and framing exercises, we have discovered that many teams within the organization want concrete goals that can be attained during the journey toward becoming a Dojo. So, we gathered this feedback and created the Tyro [powered by Dell EMC Dojo], which stands as the physical manifestation of the accomplishment reached by those who have completed the first two steps of the Dell EMC Dojo Path to Enlightenment. This is a center where practices as outlined by the Lean Startup and Running Lean are understood and implemented.

Sounds pretty cool, right? So what’s stopping you? Check out the chart below and get ready for the journey of a lifetime. As always, reach out to us if you have any further questions!

A Week in the Dojo

Amanda Alvarez

Amanda Alvarez

Amanda Alvarez

Latest posts by Amanda Alvarez (see all)

Hello readers! My name is Amanda and I am the Dojo’s newest member here in Cambridge. Words cannot describe how excited I am to be here! I am normally afraid of big changes, but I felt comfortable with this new beginning as I had a gut feeling this team would help me begin my career in this journey. It really helped my anxiety when Victor Fong gave everyone on the team a Lego Pokemon toy after he just returned from a trip. Here he is!

Once I met my team I jumped right into standup with literally no time being wasted to get my day started. Shortly after, I was paired to work on UI project. This exposure to code without needing documentation about it really blew my mind away. However, I get to see Ruby, HTML/CSS, git, and angular JS all in one day! Later, I got to rotate with my team to work on deploying Kubernetes. It can be challenging to understand what is going on, but that is because this is my first time really using things like Ruby or cloud technologies. My week with this new team finished with retro on Friday, which is when we all get together and talk about the good, okay, and bad things that happened during the week. I admitted in the bad category I felt ashamed for taking too longto learn, but I was reassured by the whole team these things take time and that I will get better.

So what have I learned?

  • Ask lots of questions. People want you to learn! There is no such thing as a stupid question. 🙂
  • Things will break. Sometimes it is an easy fix like adding a missing parenthesis. Sometimes it is a challenge that takes a day or two to figure out.
  • Ruby is a weird language. That is all I have to say about that.
  • DevOps is a really efficient way of rapidly delivering code.
  • Test Driven Development and pair programming made my first week feel almost seamless. I say “almost” because I have so much learning to do in order to get familiar with this kind of environment.
  • Tools such as Diego, Kubernetes, and Bosh can do many “things.” You might ask, “What kind of things?” And I could probably tell you they help manage deployment of containers and VMs.
  • Don’t be afraid to make mistakes. They’re something to be learned from.
  • Everyone has something to bring to the table. Share your ideas, even if you might be disagreeing with others.

Hopefully this gives you an idea of how much I learned during my first week, I am fortunate to be working with intelligent individuals who make up an amazing team. From my past experiences, I have never worked so closely with people as I have been since working here. No more contributing to one thing from the confinements of the cube of solitude and instead working with people on multiple project at a given moment. It is so easy to ask anyone what is going on because they are all familiar with the ongoing projects that are happening. Being able to pair with someone has definitely made my transition into this role feel easier. This team is passionate about what they do, and it really motivates me to do my best to get up to speed with their skills. At the time of this post, I have been working in this role two weeks now and the time feels like it elapsed in seconds. I wake up everyday to come to work feeling energized and thrilled to be at the office. Hopefully I can share something more technical next time!

~$ whoami
Before I go, I should probably share a few things about me. My favourite hobbies include: gardening, 3D printing, video games, and reading. This year I have successfully grown various herbs, such as basil and parsley, and I am an avid succulent/cactus collector. I like to 3D print miniatures and tiles that get painted for D&D, which I play occasionally when I find a good group to play with. I have always been a PS2 girl at heart, but I have been playing PC games for the last 4 years now. Lastly, I like to read mostly sci-fi books and I am currently reading through Stephen King’s “The Dark Tower” series. This pretty much sums me up outside of work. So feel free to reach out if you ever want to talk about what I do for work or my hobbies! I would love to get to know more people in this community. 🙂

Why The Dojo Matters a guide to digital transformation wrapped up in a scipab

a guide to digital transformation wrapped up in a scipab

Emily Kaiser

Emily Kaiser

Head of Marketing @DellEMCDojo #CloudFoundry #OpenSource #TheWay #LeanPractices #DevOps #Empathy

 

The Situation | Digital transformation has become a nuanced term. Somewhat like ice cream in the summer. When you see someone eating your favorite flavor on a hot summer day, it incites an immediate craving. You know that you want the cone, that it will bring you a sense of happiness not only in the taste, but also maybe in the social outing it will revolve around. But then you think about that bathing suit you hope to wear later in the day or the water that will then be needed to quench your thirst, and oftentimes there is hesitation in fulfilling the craving you know ultimately will bring no regret. Okay, maybe that’s a little too distilled of an explanation, but I hope you get the point. Digital Transformation. We know it is important, in fact it is the impending future no matter how much you try to avoid or deny it. But then by embarking on the journey, you also know that it will create work and a probable disruption in your comfortable ‘plan’. So you begin to question the value. And begin to cringe at the term, or try to validate your thought that the term has too much hype.

The Complication | This hesitancy and resistance in diving head first into the process actually hinders long-term success. Companies that are not investing fully all in money, support and effort are running the risk of falling behind competitors.  In order to build more qualitative products at a more rapid speed, there comes a time where the company, each of its teams and its employees need to embrace and overcome true digital transformation. But it’s hard. Really hard.

The Implication | As seen in the image attached, companies are running the risk of losing the opportunity to obtain that expected 30% revenue by 2020 where customers are investing to be a part of the movement. Not only this, but if companies don’t move quickly they will miss the sweet spot in the maturity of digital transformation that their competitors are gaining as time lapses. This most immediately causes depreciation of Net Promoter Score, which arguably now is more important than any vanity metric (i.e. how many lines of code are being written, number of commits, etc.) ever was. And once trust is lost, it is close to impossible to rebuild especially in the Fortune 500 customer base.

Position | It is now more than ever that we need to look past the nuance and move our teams toward modernization. At the Dojo, our mission is two-fold; to practice modern software development methodology (XP, Lean Startup) and to further evangelize ‘The Way’ to internal Dell EMC product teams, and to contribute to Cloud Foundry Foundation sanctioned OS projects. We are very lucky to work for a company that is investing in and understands fully that in order to stay alive, and most importantly thrive as IT leaders, we must continue to scale in this world of Digital Transformation. Our power at the Dojo lies in the buy-in from all levels.

Action | Our power as Dell EMC on the Digital Transformation world stage lies in the buy-in from every member of the company. It has been proven time and time again that customers LOVE the modern way in which we are building software. There are definitely challenges to rewiring the way that we work and the way that we measure the work we produce, but with hard work, comes not only a thrilling journey, but a highly productive one that produces amazingly positive results. There is no better time than now to jump on this Digital Transformation train.

Benefit | Use the Dojo as a testament and witness to all of the aforementioned sentiments and Digital Traction Metrics as seen in the attached image. Join us in paving the path to the Future. And eat an ice cream cone while you are at it.

Deploy Kafka cluster by Kubernetes

Introduction


This blog will show you how to deploy Apache Kafka cluster on Kubernetes. We assume you already have kubernetes setup and running.

Apache Kafka is a distributed streaming platform which enables you to publish and subscribe to streams of records, similar to enterprise messaging system.

There are few concepts we need to know:

  • Producer: an app that publish messages to a topic in Kafka cluster.
  • Consumer: an app that subscribe a topic for messages in Kafka cluster.
  • Topic:  a stream of records.
  • Record: a data block contains a key, a value and a timestamp.

We borrowed some ideas from defuze.org and updated our cluster accordingly.

Pre-start


Zookeeper is required to run Kafka cluster.

In order to deploy Zookeeper in an easy way, we use a popular Zookeeper image from Docker Hub which is  digitalwonderland/zookeeper. We can create a deployment file zookeeper.yml which will deploy one zookeeper server.

If you want to scale the Zookeeper cluster, you can basically duplicate the code block into the same file and change the configurations to correct values. Also you need to add ZOOKEEPER_SERVER_2=zoo2 to the container env for zookeeper-deployment-1 if scaling to have 2 servers.

zookeeper.yml

We can deploy this by:

It’s good to have a service for Zookeeper cluster. We have a file zookeeper-service.yml to create a service. If you need to scale up the Zookeeper cluster, you also need to scale up the service accordingly.

zookeeper-service.yml

Deploy Kafka cluster


Service

We need to create a Kubernetes service first to shadow our Kafka cluster deployment. There is no leader server in terms of server level, so we can talk to any of the server. Because of that, we can redirect our traffic to any of the Kafka servers.

Let’s say we want to route all our traffic to our first Kafka server with id: "1". We can generate a file like this to create a service for Kafka.

kafka-service.yml

After the service being created, we can get the external IP of the Kafka service by:

Kafka Cluster

There is already a well defined Kafka image on Docker Hub. In this blog, we are going to use the image  wurstmeister/kafka to simplify the deployment.

kafka-cluster.yml

If you want to scale up Kafka Cluster, you can always duplicate a deployment into this file, changing KAFKA_BROKER_ID to another value.

KAFKA_CREATE_TOPICS is optional. If you set it to topic1:3:3, it will create topic1 with 3 partitions and 3 replicas.

Test Setup

We can test the Kafka cluster by a tool named kafkacat. It can be used by both Producers and Consumers.
To publish system logs to topic1, we can type:

To consume the same logs, we can type:

Upgrade Kafka


Blue-Green update

Kafka itself support rolling upgrade, you can have more detail at this page.

Since we can access Kafka by any broker of the cluster, we can upgrade one pod at a time. Let’s say our Kafka service routing traffic to broker1, we can upgrade all other broker instances first. Then we can change the service to route traffic to any of the upgraded broker. At last, upgrade broker1.

We can upgrade our broker by replacing the image to the version we want like:

image: wurstmeister/kafka:$NEW_VERSION, then do:

After applying the same procedure to all other brokers, we can edit our service by:

Change id: "1"to another upgraded broker. Save it and quit. All new connections would be established to the new broker.
At the end, we could upgrade broker1 using above step. But it will kill previous connections of producers and consumers to broker1.

Spreading The Way Announcing the Dojo in Bangalore!

Announcing the Dojo in Bangalore!

Emily Kaiser

Emily Kaiser

Head of Marketing @DellEMCDojo #CloudFoundry #OpenSource #TheWay #LeanPractices #DevOps #Empathy

It is with unbelievable excitement that we are officially announcing the opening of our third global branch with a Dell EMC Dojo in Bangalore! By sharing our DevOps and Xtreme programming culture, including but not exclusive to the practices of pair programming, test driven development and lean product development at scale, we have the deepest confidence that Bangalore is the geographical mecca that sets the tone of Digital Transformation we hope for in the larger company.

So what does this mean beyond the logistical rollercoaster that comes with opening a new office? Well, I’m glad you asked!

We are Hiring! Over the next few weeks, we will be rapidly and qualitatively (only because how else would we operate?) looking for and interviewing developers and product managers interested in becoming a part of this exciting new Dojo from its inception. So, if you know of anyone in the area that may be interested, please point them in the direction of Sarv Saravanan (sarv.saravanan@emc.com) who will be handling the process on the ground.

 

Otherwise, stay tuned on our team’s impending growth, engagement (both here and in India), and overall adventure!

Until next time…

 

Doers for Today, Visionaries for Tomorrow and Change Agents for Always! We Truly Are The Trifecta

We Truly Are The Trifecta

Emily Kaiser

Emily Kaiser

Head of Marketing @DellEMCDojo #CloudFoundry #OpenSource #TheWay #LeanPractices #DevOps #Empathy

The Dell EMC Dojo has a mission that is two-fold; we contribute to open source Cloud Foundry, and we evangelize ‘the way’ (XP, Lean Startup, etc) by engaging with internal Dell EMC teams in a purely DevOps manner. Our mission is direct with a scope that some could argue is boundless. By practicing ‘the way,’ hours, days, and weeks fly by as we push code to production at times every few minutes. Not only is our push to market rapid, so is our overall productivity. Oftentimes teams working with us nearly guffaw when they come to our office in Cambridge, MA and are able to see the ‘wizard(s) behind the curtain.’ We are asked how we keep three to five projects on track while also engaging with internal teams, planning large technical conferences, and working in the realm of R&D in our greater TRIGr team with an east coast contingent of only eight people and a west coast contingent of five. The secret? We LOVE what we do!

 

A team with empathy at its core, there is never a moment when a task seems impossible.

Truly, we could be featured on one of those billboards along the highway stating that there is no ‘I’ in ‘Team.’ Two baseball players carrying an opposing team member across Home because she/he has hurt themselves, a photo of all of the characters from Disney’s “The Incredibles,” The Dell EMC Dojo team… Take your pick… TEAMWORK. Pass It On.

In all seriousness, the pace at the Dojo can be absolutely exhausting, and with such a small team, the absence of one person (which let’s face it, vacation and life needs to happen at points) could in theory be a huge deal. But, because DevOps is what we live and breathe, any member of the team can fill this gap at any point, truly putting to practice the idea that there doesn’t have to be and should never be a single-point-of-failure. Albeit the industry or sector, what more emulates the ‘Go Big, Win Big’ message than this? By continually pushing ourselves to pair and to up-level the knowledge of our entire team, we never wait until tomorrow to take action. There is no need or desire to.

 

Agility is not a term we just talk about, but is simply inherent to everything we do.

With the combination of the rapidly changing market (externally and internally) and the pace in which we work, we at the Dojo have learned that we must stay on our toes. For those reading this that are familiar with sports, one of the first lessons learned in soccer is to never plant your feet. Holding such a stance allows for the opposing team to outpace you when the unexpected happens, which is most of the time. Same goes here. Pivoting is now second nature for us, and it doesn’t come with the scares. Instead, it is actually exciting when we are able to take data and identify ways in which we can better align with efficiency and effectiveness of software and methodology; to truly keep the user omnipresent in everything we do. We are happier. The ‘customer’ is happier. It is a (Go Big) win-win (Big) game. The cool thing too is that the more we practice this, the more we also feel somewhat like we can predict the future, because we begin to see trends before they are even a thing.

 

 

Doers for Today. Visionaries for Tomorrow. Change Agents for Always.

Do You Hear That? It’s the sound of Keyboards! Call for Papers | Cloud Foundry Summit Silicon Valley 2017 is quickly approaching!

Call for Papers | Cloud Foundry Summit Silicon Valley 2017 is quickly approaching!

Emily Kaiser

Emily Kaiser

Head of Marketing @DellEMCDojo #CloudFoundry #OpenSource #TheWay #LeanPractices #DevOps #Empathy

Our brains are on fire, our keyboards are hot, and the joke in the office the past few days has been over our extreme excitement for the eventual need to buy sunscreen since our Boston winter leaves us Vitamin D deprived. Why is this the case, you may or may not be asking? Well, I plan on telling you anyway because it is just too exciting not to share!

Our team is preparing for CLOUD FOUNDRY SUMMIT SILICON VALLEY! We felt a social duty to let all of those we care about and want to be there with us for what’s sure to be the summit of the summer (how can it not be when it is being held in June in Santa Clara?!), that the last call for papers is quickly approaching (no seriously, it’s this Friday, February 17th).

Just as a refresher for those on the fence, Cloud Foundry Summit is the premier event for enterprise app developers. This year the Foundation, through market research and feedback, found that interest and industry need is engrained in the focus on innovation and the streamlining of development pipelines. For this reason, Summit 2017 is majorly honing in on microservices and continuous delivery in developers’ language and framework of choice. That is why the session tracks available will be Use Cases, Core Project Updates, Experiments, Extension Projects, and Cloud Native Java. Each session that is chosen for the conference is enabled (1) primary speaker and (1) co-speaker. The primary speaker receives a complimentary conference pass while the co-speaker receives a discounted conference pass. So what’s stopping us from getting involved? Absolutely NOTHING!

As a sneak peak to a few of the topics our team have submitted for approval, see below:

  • Adopting DevOps and Building a Cloud Foundry Dojo (Lessons Learned)
  • Lift & Shift Your Legacy Apps to Cloud Foundry
  • How to Develop Scalable Cloud Native Application with Cloud Foundry
  • Enabling GPU-as-a-Service in Cloud Foundry
  • Blockchain as a Service
  • Avoiding pitfalls while migrating BOSH deployments
  • Spring Content: Cloud-Native Content Services for Spring

 

So, now what’s stopping YOU from getting involved? Submit papers here: https://www.cloudfoundry.org/cfp-2017/ and/or register here: https://www.regonline.com/registration/Checkin.aspx?EventID=1908081&utm_source=flash&utm_campaign=summit_2017_sv&utm_medium=landing&utm_term=cloud%20foundry%20summit&_ga=1.199163247.1732851993.1460056335

Last but definitely not least, let us know if you plan on coming—we are more than happy to share sunscreen 🙂 We cannot wait to see you there!

Thriving in a world of disruption – the “Dojo Way” Brian Roche, Lead of the @DellEMCDojo

Brian Roche, Lead of the @DellEMCDojo

Brian Roche

Brian Roche - Senior Director, Cloud Platform Team at Dell EMC. Brian Roche is the Leader of Dell EMC’s Cloud Platform Team. He is based in Cambridge, Massachusetts, USA at the #EMCDojo.

We in live a world where ideas can be dreamt up, implemented and delivered more rapidly than ever before.  The pace of innovation is like nothing we’ve ever seen in our lifetime and it will likely only get faster.  Old patterns of software delivery, 12 month releases are insufficient in meeting demands of today’s marketplace.  As a result many people will face extinction if they do not change their work patterns and focus on two key objectives; customer needs and delivering software rapidly to meet that need.  Iterate and repeat.

This disruption creates opportunity if we’re in the right position to take advantage of the constant changes. In fact it is possible thrive in this new world and lay the foundation for a successful future.  At the @DellEMCDojo we have found that better way. The Dojo was created for 2 simple reasons. First to adopt a DevOps culture to achieve lower cost innovation, more rapid product delivery and to build innovative solutions that meet the needs of customers.  Second, to contribute to OS Cloud Foundry.  All of this is important because we not only demonstrate to our customers that we walk-the-walk and talk-the-talk but we also can respond to their market needs and deliver solutions to them to enable and empower them to compete effectively.

 

The dojo methodology is important but it’s what we create with this new way of working that is most important.  After all, this is a business, revenue is the score card and we measure the success of our software based on user adoption.  Here is a brief run through of the projects we’ve worked on in recent months.

 

Persistence in Cloud Foundry 

Cloud Foundry is WAY cool & 12 Factor Apps are WAY cool too BUT you and I don’t just have to worry about 12 Factor Apps.  We have legacy apps that live in our family that we still need to pay attention to. Our position is there should be a place for these legacy apps in our cool New World called Cloud Foundry. That’s why we enabled container persistence in Cloud Foundry.  Shipping in PCF 1.9 customers can take advantage of this functionality by mounting NFSv3 volumes from within their containers.  The obvious first technology integration was with Isilon; customers can now mount Isilon volumes.  As a result we have created a world where 12 Factor apps and non 12 Factor apps can live together and experience the benefit of Cloud Foundry.  We are actively developing this technology for and with customers and the response thus far has been very positive.

 

GPUaaS and Cloud Foundry 

We are seeing a growing demand for big data processing for one simple reason, the ability to make intelligent decisions about data is as important as continuous delivery.  Running those big data workloads that require massive processing power is not easy for Cloud Foundry developers today.  One obvious challenge is they cannot choose where these application workloads will be executed.  Leveraging the great work that Jack Harwood and the team in China has done on GPUaaS we were able to integrate this with Cloud Foundry.  The result is application developers will now have choice—they will be able to choose where their workloads are run leading to even greater efficiency and value from their information.

 

Blockchain and Cloud Foundry 

Blockchain technology comes up more and more when the larger Dell EMC talks to customers.  The first question is often ‘what is it and how can we leverage it?’  Up until recently we didn’t have an opinion on this technology.  So we kicked off a project with the following goals:

 

1.      Understand the different Blockchain distributions

2.      Identify ways in which we could integrate Blockchain with Cloud Foundry

3.      Make this available to the community so we can all iterate on this together

 

I’m pleased to say we now have a Blockchain implementation with Cloud Foundry and are happy to share not only the code/implementation but also our learnings.  Together as a community we can go far in developing this technology to solve real business problems.

 

 

The Dojo Effect

The Dojo team has come a long way in two years, now everyone wants to create a dojo.  The brush fires have been lit and the ‘dojo way’ is spreading.  A word of caution for those eager to get started quickly; while we’re happy with the enthusiasm and the willingness to change work patterns, there’s more to building a dojo and adopting DevOps than changing the physical space.  This methodology is nuanced, you don’t know what you don’t know especially early on.  It can be easy, especially early on in the adoption phase, to get lost and give up.  To embrace this new way of working it’s a good idea to have help from your friends, like we did from Pivotal and Pivotal Labs.  That’s where the dojo team comes in.  By working with us in a 6 week engagement we will pair with you, teaching you to fish so you form a solid foundation from which to build on after you leave.  We’re pretty strict in implementing Lean Startup and Running Lean to the letter.  Why? Because we know when you leave you’re going to relax so we want to keep the standard high knowing you may relax later.  There’s no better way to transform than to work with the @DellEMCDojo team.

Lastly, at the heart of our success is the dojo team – the people.  The incredibly talented individuals that have adopted these new work patterns and refine their art every single day by practicing at the dojo.  I would like to acknowledge and thank an amazing dojo team for riding the waves of change and finding ways to be successful regardless of what obstacles are thrown in our path.  You and your teams can find a way to thrive and enjoy the rapid pace of innovation in the same way the dojo team has.

Until next time, c ya.

Dell EMC Dojo at Hopkinton! Reviewing what we covered, and what we learned

Reviewing what we covered, and what we learned

Hey again everyone! We’re writing out today to talk about a few topics that we covered during our time at the Dell EMC Dojo Days in Hopkinton. We met with a lot of great minds and took plenty of input into how we work. We also gave a lot of insight to passersby in what we did and how we worked.

Firstly, Brain Roche and Megan Murawski debuted the famous “Transformation Talk”. We normally give this presentation in preparation for an engagement with another team, but in this case, it was given to allow open criticism and circulation of our methodology to the rest of the company. We cover in this presentation: pairing, and why it’s important to our process, why we use TDD (Test Driven Development) (and why you should too!), and our weekly meetings including Retros, IPM, and Feedback to name a few. We had plenty of great ideas and questions, as usual, and we realized twenty minutes over time that we couldn’t get Brian off the stage.

Xuebin He eventually got Brian off-stage for a talk he conducted on CICD (Continuous Integration, and Continuous Deployment). Xuebin being one of the developers at the Dojo allowed him to be a bit more technical in his talk, and cover some of the programming practices and tools we use to achieve this at the Dojo. Concourse is our tool for running our beautifully constructed tests, along with standard mocking design patterns and the code quality produced with TDD.

We picked up again on Tuesday at 1145 to talk about why a PaaS exists, and why it’s important. That talk, given by yours truly, was focused on some of the common technical roadblocks that keep developers, customers, and managers from being able to work efficiently; as well as the ways using a PaaS can solve those problems to build a better business.

To containerize applications for a PaaS, we would need to learn basics like “What is a 12 factor application, and what’s a container?” Thinh Nguyen stepped in and gave a great description on how we use guiding principles while developing our application environment to be better for us and our customers.

Throughout all of our talks, we worked away on two pair stations very carefully brought from our lair in Cambridge. We gave away some free swag, some free candy, and raffled off some super giveaways. We thank everyone involved in preparing and executing these few days for their hard work. We also want to give a huge thanks to everyone who attended our talks (rambles) and participated in some mind-expanding conversations.

Finally, I want to close with a few notes. We always enjoy fresh perspective. If you had more to say, or you missed us during our time and you want to start a conversation, leave a comment in the comment section! If you don’t want to comment here, then drop us a line in my email. We’d love to hear from you.

Until next time, remember: Cloud Foundry, Open Source, The Way. #DellEMCDojo.

THE EVENT OF THE SEASON Coming to Hopkinton December 5th and 6th

Coming to Hopkinton December 5th and 6th

Emily Kaiser

Emily Kaiser

Head of Marketing @DellEMCDojo #CloudFoundry #OpenSource #TheWay #LeanPractices #DevOps #Empathy

Before reading this blog post, I suggest that you and anyone that may be reading over your shoulder sit down. In your chairs? Great, because the excitement you are about to feel will surely leave you overwhelmed.

 

The event of the quarter is right around the corner! Please consider this your personal invitation to join us for DOJO DAYS next Monday and Tuesday, December 5th and 6th from 10 am to 4 pm in the 176 Café out at Dell EMC in Hopkinton.

official-dojo-days-logo

DevOps is a hot word in the world of technology. It represents a way of working and technique that aims at making the customer omnipresent in everything that is created and delivered. Companies today consider this way the future.

For this reason, Dell EMC and Pivotal paired to create the first ever Dell EMC – Pivotal Cloud Foundry Dojo. Our goals are centered around personal, team and company transformation. Through the practice of modern software development, we spend our days contributing to Cloud Foundry Foundation sanctioned Open Source projects through R&D modernization and methodology known as ‘the way’ (XP, Lean Startup).

Many know us as the team in Cambridge with great food and beverage (no really, it’s amazing- come visit us to see for yourself). We realize, though, that the commute isn’t ideal for most. So, we bring you Dojo Days to experience #adayinthelifeofthedojo, with a replication of our office environment and our team in action representing the steps we took to transform.

In addition to seeing #adayinthelifeofthedojo, you will have the chance to pair with us, join our team for lightning sessions that are driven by the audience’s goals (schedule below) and have the chance to win a Dell EMC Dojo branded Patagonia, S’well water bottles, t-shirts, and more!

 

The schedule of the lightning sessions are as follows. Please come by the Café day of to sign up and/or just drop in:

Monday, December 5th:

11:45 am to 12:45 pm: Steps to Transformation starring Brian Roche and Megan Murawski

2:00 pm to 2:30 pm: TDD and CI/CD starring Xuebin He

 

Tuesday, December 6th:

11:45 am to 12:45 pm: PaaS, and Why your Developers Care starring Gary White

1:30 pm to 2:00 pm: Factor, Cloud Native, and Containers (oh my!) starring Thinh Nguyen

 

If you have any questions, please contact Emily Kaiser at Emily.Kaiser@dell.com. Otherwise, we cannot wait to see you, your team, and all of your friends out in Hopkinton next week!

Follow Us on Twitter

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.