Home > Blogs > Open Source @VMware

Hard(ware) Lessons Learned: Getting Started with Open Source Hardware

There’s a familiar face on OpenSource.com.

One of our most enthusiastic VMware Open Source experts, John Hawley, shared a must-read article with the : 8 Ways to Get Started with Open Source Hardware.

“Let’s start off by pointing out that hardware is hard, it’s complicated, sometimes esoteric and the tools you may be using are not always the most user-friendly. … Lessons are learned when things go wrong, and you usually get an interesting story to tell later.”

John Hawley, VMware Open Source Developer

In his OpenSource.com piece, John highlights eight steps you need to take once you figure out what you want to build. Here are the first four steps to get your started:

  • Find an electronic design automation (EDA) tool. John recommended a few user-friendly options, such as Fritzing, gEDA and KiCad.
  • Design your board in the tool. For your first time around, John suggests keeping it small and simple before building up from there.
  • Export the design for manufacturing.
  • Find a board house. Ever heard of OSH Park? That’s the board house John uses for his open source hardware projects.

Four more steps remain in John’s quest to build the hardware he needs. After all:

“That’s what open source hardware is: A community of people making things and sharing them so that everyone can make their own things and build the hardware that they want—not the hardware they can get.”

Follow John’s upcoming OpenSource.com contributions via RSS or catch him on Twitter @warty9.

Because you liked this blog:

OpenStack Summit Takeaways

By Mark Voelker, OpenStack Architect at VMware

Another OpenStack Summit is in the books! Last week I attended my 13th OpenStack Summit in Boston, Massachusetts. Part of what makes OpenStack Summit such a great event is the mix of activities and people. While I saw a lot of familiar faces and spent a lot of time catching up with old friends, I also met a lot of new folks—in fact, about half of the attendees at each OpenStack Summit are there for the first time

While I spent some time catching up on projects I’ve been working with for some time, I also spent some time with relative newcomers to the scene and adjacent communities. In fact, this spring OpenStack Summit hosted a number of “Open Source Days” for the first time. Open Source Days brought adjacent communities to the OpenStack Summit so attendees could get the best of all worlds. The roster included Kubernetes, Open vSwitch, OPNFV, CloudFoundry, and more. Specific use cases were on display too, with a lot of sessions and hallway conversations focussing on NFV and container workloads atop OpenStack.

Boston

If that wasn’t enough open source, adjacent open source technologies also made it to the main keynote stageful the second edition of the Interop Challenge. I joined a large group on stage to do a live demonstration of a cloud-native workload deployed without modification on 15 different OpenStack clouds. This time around, we enlisted a little help from our friends at CoreOS and CockroachDB. We deployed Kubernetes on CoreOS guest instances, and then spun up a containerized CockroachDB cluster on top. While that in itself was a great testament to how much more portable workloads on top of OpenStack have become and how diverse the ecosystem is, we also spent some time this year to demonstrate not just repeated copies of the same workload, but a single app running across clouds. VMware joined a group of others to connect our CockroachDB cluster into a single large, geo-distributed database cluster spanning several clouds. As we see hybrid cloud or multi-cloud use cases go from thought experiment to production deployment pattern, this demo was a timely reminder of how fast the cloud ecosystem is evolving—and how fast OpenStack is moving to keep up. OpenStack is now approaching it’s seventh birthday, while Kubernetes is just shy of two years on from its 1.0 release and CockroachDB launched it’s 1.0 release on May 10th—the day after our on-stage demo!

While a lot of energy went into use cases in which OpenStack is rapidly growing and adjacent open source technologies that OpenStack users are increasingly adding to their portfolios, plenty of time was also spent on traditional OpenStack projects. Boston was the first OpenStack Summit under the new Summit format. Following last year’s OpenStack Summit in Barcelona, the community split the Design Summit portion of the conference out into a separate event called the Project Team Gathering (the next of which will be held in Denver later this year) so project developers could spend more time focussing on development.

The split also freed up some time at the Summit for developers to spend more time in “fishbowl” sessions with users—a new series of events within the Summit called “The Forum”. The Forum sessions I attended were mostly spent gathering feedback from operators and users about what to work on next to make sure OpenStack remains a good fit for production use. Generally, the feedback seemed to focus on a few key themes: emerging use cases (such as NFV and containers) and continued hardening of widely-deployed projects (like Nova, Cinder, and Neutron).

One particular topic that generated a lot of interest was a new addition to one of the oldest OpenStack projects: Nova. In the new Ocata release of OpenStack, all Nova deployments use Cells v2, a reimagined version of the experimental Nova Cells feature that was introduced years ago as a way to help Nova scale to larger deployments. Starting from Ocata, all Nova deployments will be a “cell of one”, which support for multiple cells landing in future releases. A fair amount of time was also spent on the Nova placement API, which was initially introduced in the Newton release and is increasingly important to scaling up deployments and alleviating expensive rescheduling events from the Nova scheduler.

All in all, Boston was another great OpenStack event: a steady hum of activity mixed with a few new twists.  We’re looking forward to the PTG in September, and the next OpenStack Summit in Sydney in November—see you there!

Don’t miss Misbah Mahmoodi’s deep-dive into how telcos can benefit from open source platforms like OpenStack. Stay tuned to the OpenSource blog for more.

OpenStack Summit Recap

By Ben Pfaff, Principal Engineer at VMware

I attended the OpenStack Summit, the fifth Summit for me, in Boston this week, May 8-11. For me, the highlight was Open Source Days, a new element for this summit. For Open Source Days, the OpenStack Foundation selected 11 open source projects related to OpenStack, Open vSwitch among them, and gave each of them a room for a day for presentations. OpenStack handed out these rooms at no charge, which is incredibly generous given that conference space ordinarily costs thousands of dollars for a room. They additionally gave 10 free registration codes to each open source project to distribute to speakers, also incredibly generous given that full registration is $600 or more.
OpenStack logo

For the Open vSwitch Open Source day, we sent out a call for presentations back in February, received several submissions, and accepted about 10 talks, each 10 to 20 minutes long, plus an hour-long tutorial session. We held the Open Source Day on Wednesday. I was anxious about attendance before it started–I always am–and the first few talks were lightly attended. Around 11 am, the room started filling up for a talk about NFV performance, and from then on the room was well filled. Over 100 people attended my tutorial on using OVN, the open source network virtualization system that is part of Open vSwitch, with OpenStack in the afternoon.  The day of talks wrapped up around 5:20 pm. The event was a big success and I hope that they will make Open Source Days a regular feature of their conferences.

In addition to the Open Source Day, on Monday I gave a joint talk in the main conference on the latest features and the future of OVN, with Justin Pettit from VMware and Russell Bryant from Red Hat.  I also had numerous meetings, lunches, and dinners with folks who have an interest in Open vSwitch and OVN.

A video recording from my talk about OVN is already available on the OpenStack website at https://www.openstack.org/summit/boston-2017/summit-schedule/events/17833/openstack-and-ovn-whats-new-with-ovs-2-7. Over the next few weeks, audio recordings and slides from the Open vSwitch Day talks will be posted and made available on the OVS Orbit podcast at https://ovsorbit.org and at http://openvswitch.org/.

Awareness Unleashed: DevPulseCon Recap

By Ben Pfaff, Principal Engineer at VMware

I attended the DevPulseCon conference, held at the Computer History Museum in Mountain View, on April 20 and 21. For readers already familiar with this event, you might be shaking your head, wondering if you read that right. Or maybe you’re thinking I got my events confused. Why would someone like me be going to the DevPulseCon conference? Admit it: you’re a little curious now, aren’t you? Read on and I’ll explain.

The conference, which VMware sponsored, was one full day of technical talks and panel discussions followed by a second day of workshops. The technical talks included speakers from eBay and Mesosphere. Two of the tech talks covered open source software, including one that talked about how to assemble do-it-yourself IoT devices at home. The panel discussions were actually worth attending (not always the case at tech conferences).

DevPulseCon

The first workshop was about machine learning, and I successfully followed along on my own laptop and gained some experience actually playing with machine learning algorithms that I’d only heard about before, using the open source “pandas” library for Python. The second workshop was about the Clarity open source web framework, which I learned VMware had founded and continues to develop. I did not manage to follow along with this second workshop, but this was mainly due to my own “conference fatigue”, since paying complete attention for two days in a row is really difficult.

It was a quality tech conference. What makes it stand out further is that DevPulseCon is by and for women, primarily engineers and developers, so all of its speakers and (almost) all attendees are women. I am not a woman, but I was among a few men privileged to attend by special invitation from Rupa Dachere, the creator and director of DevPulseCon and founder and executive director of CodeChix, an all-volunteer 501(c)3 charity that educates advocates for women engineers in industry.

This is a grassroots event. There’s no tone-deaf messaging that must have originated from a corporate team trying to figure out how to market to women. I honestly expected to feel awkward at least a few times during the two days, as a man among hundreds of women, but in fact I felt comfortable and even welcomed. I made myself useful in a few small ways at event setup and teardown and by lending a few pieces of A/V equipment.

Based on attendance and quality, I expect DevPulseCon to keep going for years. For more about DevPulseCon, please see http://devpulsecon.squarespace.com, or listen to the podcast that Rupa and I recorded before the event, at https://ovsorbit.org/#e29. For more about CodeChix, see http://codechix.org.

 

Meng Chow Speaking at Women Who Code Connect 2017 on 4/29

Women Who Code (WWCode) is a global non-profit dedicated to inspiring women to excel in technology careers. While software development is one of the fastest growing job sectors in the global economy, it’s also one that’s notorious for being predominantly male. Organizations like Women Who Code aim to change that through advocacy, education, mentorship, and awareness.

 

Since 2011, WWCode has connected over 80,000 women globally, produced 4,200 free technical events in 20 countries, and awarded over $1,000,000 in educational scholarships and tickets.

 

This Saturday, April 29th, WWCode will be hosting their annual Connect event featuring a variety of speakers including VMware’s own, Dr. Meng Chow. Meng’s topic: Open Source – Compliance, Quality, and Viability. Meng is a Program Manager in VMware’s Open Source Program Office.

WWCode Connect

Earlier this week, we caught up with Dr. Chow as she gave her thoughts on the event, the open source world, and other things.

 

Meng, tell us a little more about the talk you’ll be giving on Saturday at Connect.

 

Dr. Meng Chow: The title of Saturday’s presentation [at the Connect event] is “Compliance, Quality, and Viability”. And really, I think the idea here is looking at what we do inside VMware and then expanding some of those things to what we do in open source. As it is, open source is a natural extension of our corporate philosophy and core values here at VMware. So that’s the backdrop of why I want to talk about open source at Connect.

 

I want to really share the great things we are doing at VMware in open source. Complying in terms of open source licenses is something we take very seriously – and on top of that, also bringing quality and viability into consideration.

 

How do you talk about these values, and the importance of open source?

 

Open source, as you know – it’s important for any development strategy. It reduces development cost, it helps accelerate time to market because you don’t have to build everything yourself or start from scratch, and it gives you a shorter release cadence to release products much faster. On top of that, you have all these passionate users from the community coming together to share ideas. And that is absolute total grounds for innovation.

 

When people think about open source, people think free. You use it at no cost. It’s like free beer. In my talk, I want to set the stage and ask, “What is so successful about open source and why does it open all these new possibilities for us?”

 

Really, the answer to that – the philosophy behind open source is the freedom to access new technology. It’s free as in freedom, not free beer. You have a community of users that come together – where everybody can participate, nobody owns exclusive rights to the code – and that shared development by users is what contributes to the richness of the software, in terms of new features, and new versions in open source.

 

I also want the attendees to know – with great freedom, comes great responsibility. There are implications and consequences that come with open source, especially when you include it in your product. I’ll be talking about support, license compliance, and business alignment.

 

That’s a great point. When people think open source, they think it’s free from any license obligations. The word free often gives the implication as if there are no restrictions or things you need to be concerned about – and that couldn’t be further from the truth. There are always licensing considerations to be aware of and be compliant with, and understand the different variations of an open source license to make sure those variations and licenses are aligned to your business objective. Users need to be aware of that before they go into open source and wrapping that into their software. If it’s not compliant, you’re going to run into big problems.

 

Absolutely. Not just on the legal side, but in terms of how you support it on your own. There are plenty of ramifications that can pop up if you’re not careful. Then there the big thing around security vulnerabilities – how do you make sure you can take care of them? With open source, anyone can get involved. It’s like a playground for security engineers, where all these vulnerabilities are discovered. When something gets discovered, you must have the infrastructure to pull in those updates, make sure it gets to your product. That’s something we take to heart at VMware – being very clear about communication. Getting hot fixes to the product team and make sure those happen in a timely fashion.

 

One of the key takeaways here, is that the product quality is dependent on the quality of the open source software. The quality of the open source software is dependent on the open source project. Additionally, choosing the right components is key to the viability of the project. I’ll finish my presentation with a discussion on the framework VMware uses to assess viability of open source software.

 

Last, but not least Meng, what do you see as the primary value for attendees of WWCode Connect?

 

VMware is very strong in terms of participating in these inclusion activities and making sure women have a voice in the industry. Women Who Code is certainly one of those forums that allows women to get together, to share ideas, to share best practices. It excites me to be a part of the Connect 2017 conference and help inspire the next generation of women engineers.

 

The Women Who Code Connect 2017 is on Saturday, April 29th, in San Francisco, California. You can get tickets by clicking here.

Java and Perl join the vSphere Automation SDKs in Github

By Alan Renouf, Sr. Product Line Manager, VMware

vspheresdk

On March 9th 2017 VMware this post here announced the open sourcing of some of VMware’s key Software Development Kits (SDKs) allowing partners, automation engineers, DevOps teams and system admins a wealth of tooling to access the new vSphere Automation REST APIs.

These SDKs were for Python and REST, the community feedback and commitment received was fantastic and we want to thank anyone who committed changes and worked with us on the SDKs.

So Whats New?

Today I am pleased to let you know that we at VMware are adding further to our commitment to Open Source and better developer collaboration have added two additional new GitHub repositories to allow even more collaboration and ease of access to the additional languages of Java and Perl.  If you access the main page here you will now see additional buttons for these languages and an overview of the existing SDKs.

The Github repositories can be accessed directly here:

As a reminder, these SDK’s currently cover the following features with more to be added in the future:

  • VM Basic Lifecycle
  • vCenter Server Appliance (VCSA) Management APIs
  • vCenter Tagging (Available since vSphere 6.0)
  • vSphere Content Library (Available since vSphere 6.0)

Does this help you? Let us know in the comments!

We look forward to working with you and our Open Source SDKs!

Stepping It Up

The Linux Foundation is an organization that I have been deeply involved it for many years. I was a founder and Board member of the Free Standards Group (FSG) when we merged it and Open Source Development Labs (OSDL) to create the Linux Foundation in 2007. (For open source history buffs, technically the Linux Foundation states that as the legal successor of OSDL it was founded in 2000).

I have always seen the Linux Foundation’s role as the steward of the shared ecosystem that allows us to accelerate open technology development and commercial adoption much more than just “the place where Linus works.”

When I joined VMware last summer, one of my goals was to step up our engagement in this ecosystem. To me that meant many things:

  • Improve our internal processes around open source;
  • Increase our contributions to the open source communities;
  • Release more of our own work as open source projects; and,
  • To double down on our engagement with the Linux Foundation.

A member of the Linux Foundation since 2008, VMware upgraded its membership from Silver to Gold earlier this year. Following that change, I decided to run for one of the Board seats allocated to the group of Gold members. I’m thrilled to serve as a representative of an impressive group of companies on the Board. And I look forward to working with Jim and the rest of the Board to continue the work towards our shared goal – open technologies that help our customers to more successful outcomes.

In so many ways, it feels like I have been doing this forever. And in so many ways, the work has just begun. I look forward to this next chapter.

Community Updates on the Open Source vSphere Automation SDKs

VMware recently open sourced our vSphere Automation SDKs on GitHub, which was a huge deal. Equally huge, we have received the first external update to the vSphere Automation SDK for REST repository. It was from community member Ludovic Rivallain whom became the first external contributor. His commit features 111 new requests to manage the vCenter Server Appliance (VCSA) when used with the Postman REST client!

Catching Up with the Committer

Ludovic Rivallain
I had the chance to ask Ludovic a couple questions about himself and how he came about contributing to the repository. I’ll start with some background on Ludovic, whom is a Senior Virtualization Engineer at SII Group, a French IT consulting company. His focus varies between VMware infrastructures and multiple IaaS/PaaS/SaaS offerings, but is an automation fanatic regardless. He uses a mix of Python, PowerShell, and Bash scripts regularly to perform his automation workflows and tasks. Ludovic can be found at the Twitter handle @lrivallain and also blogging at: https://lri.ovh

Ludovic first came across the repository while doing some investigation for an R&D project which requires vSphere 6.5. One of the largest areas he wanted to research was around the VCSA’s native backup capabilities. He had already started composing some of the requests, when he discovered the SDK repo. From the repo’s samples, he was able to use those as a template to build out the commit, which ended up at 111 total requests.

Exploring the New Collection

As part of Ludovic’s commit, there has been a new Postman Collection added to the SDK which is called: vSphere Automation REST Resources for Appliance. This collection has a similar folder structure to the prior available collection, so the user experience is exactly the same. The samples include such areas as Access, Health, Monitoring, Networking, Recovery, and the TechPreview areas as well.

New Postman Collection

If you haven’t had a chance to start utilizing the SDK for REST yet, here’s a blog post to help: Getting Started with the vSphere Automation SDK for REST

Taking an in-depth look at the Recovery options included with this new collection, since Ludovic is correct about them being an important part of the release, we can start by expanding the Recovery folder and checking out the available options. There’s the ability to retrieve a list of the backup jobs, obtain the details of a specific backup job, validate the location and fields for a backup job, create a backup job, cancel a running backup job, and gather information about parts of the backups.

First, we can retrieve a list of the backup jobs by selecting the ‘Backup Job’ option. This performs a GET request to: /appliance/recovery/backup/job

Request to list backup jobs

We can then create a new backup job. We’ll start by validating the inputs for the backup job itself with the ‘Backup job – validate’ option. This performs a POST method to: /appliance/recovery/backup/validate

Request to validate a backup job

After receiving the status of “OK”, we can then make the call to perform the backup. We’ll start by copying the body from the validate request, select the ‘Backup job – Create’ option. This performs a POST method to: /appliance/recovery/backup

Request to create a backup job

From that point, we can follow along with the status of the backup job. Start by copying the output from the ‘id’ field on the prior request. Followed by selecting the ‘Backup job – Details’ option. This performs a GET method to: /appliance/recovery/backup/job/{{appliance_backupjob_id}}

However, in the URL, replace {{appliance_backupjob_id}} with the job’s ID. After making the request, you should receive the current status of the backup job.

Request additional details about a backup job

Conclusion

The new Postman collection is a terrific addition to the vSphere Automation SDK for REST. I only skimmed the surface of its capabilities. We certainly encourage everyone to download it and give it a try. Please also feel free to reach out and let us know how it is and what could be added to make it even better, or even make the contribution yourself!

I’ll also close this blog out with a quote from Ludovic:

Everyone, contribute!! Some very little things, that might seem insignificant can help many other people who work in the same domain and VMware’s open source projects are a very good place to start. And last but not least, I want to emphasize on the high quality of the available documentation for vSphere Automation SDK for REST.

Interview with Ben Pfaff, on the Open Networking Summit and More

The Open Networking Summit took place on April 3-6 – where Enterprise, Cloud and Service Providers gathered in Santa Clara, California to share insights, highlight innovation and discuss the future of open source networking.

One of the attendees at the Open Networking Summit was Ben Pfaff, Principal Engineer at VMware. Ben is a lead developer of the Open vSwitch project and led the development effort of the OpenFlow reference implementation. We caught up with Ben after the show to hear his thoughts on the show.

This blog represents part 1 of our interview with Ben. In part 2, you’ll hear more about one of his main projects, Open vSwitch, of which is he is a lead developer.

Hey Ben, thanks for taking the time to speak with us today. How was Open Networking Summit?

 

Ben: So, Open Networking Summit (ONS) actually consists of two events – there might be more, but I was involved with two. ONS is the big event itself. There is also the Symposium on SDN Research (SOSR). This is an academic conference that accepts papers. I was on the program committee for that and deeply involved in the research papers and selecting a program there. On Monday morning, I was the session chair for the first session there.

There were some pretty fantastic papers at the conference. My favorite one – there was a system called “NEAt: Network Error Auto-Correct”. The idea here is that the system keeps track of what’s going on with your network and notices problems and automatically corrects them. It was designed for an SDN setup where you have a controller that is responding to changes in the network and telling systems what to do.

Any particularly memorable papers from the Symposium on SDN Research?

We saw a paper on bug finding, called BigBug. It was a way to collect all of the bugs one system had found–which often amounted to thousands–and classify them, so it was easy for programmers to track them down.

Did you see more papers submitted this year at SOSR?  

Yeah, we did. I think the number of paper submissions was increasing based on last year’s number – the deadline this year was later compared to last.

You had a presentation at ONS – Can you provide a little bit of background as to what you covered?

Justin Pettit (also a lead developer on Open vSwitch) and I do these talks often. This time, we wanted to do it more interactive. We had 50 minutes, but we only used a half hour to take questions – and we got a lot of them. A few like“How can I use this?” or “Is this supported?” but also some deeper questions about specific features or our future vision for different aspects of the system.

The slides from our Open Networking Summit talk will be available here.

Anything in particular you found exciting at Open Networking Summit?

One thing – I hadn’t quite realized in the moment, since this is my first time attending in full – ONS is just swarming with people in the industry, both on the management side and technical side. You run into all kinds of people in the industry. The other thing I noticed, and that the Linux Foundation is really emphasizing, is that every open source Linux Foundation project had a session there.

What do you see as the main value of attending something like ONS?

I think the biggest value of attending a conference like ONS is the people that are there – your fellow attendees. You can run into so many people. Half are doing startups with these crazy ideas that we’re able to learn from. There is the expo, and seeing what products that people are putting out. Usually, I’d say the keynotes provide a lot of vision, but this year they tended to be a little more retrospective.

Special thank you to Ben for taking the time to chat with us! You can follow Ben on Twitter at @Ben_Pfaff.

Project Clarity at NG-Conf in Salt Lake City, Utah

This week, April 5th, 6th and 7th, you’ll find VMware and the Project Clarity team at NG Conf – the world’s original Angular Conference – in Salt Lake City, Utah.

NG-Conf

And while you can learn about Clarity at the VMware booth, your best bet will be to stop by the Clarity booth. There you’ll find the Project Clarity team showcasing the latest with Project Clarity, engaging with the community and demonstrating the latest features and enchancements.

ProjectClarity

We caught up with Jehad Affoneh, project lead for Clarity, to get more details on what this week’s activities.

 

Thanks for talking with us today, Jehad. What is the VMware team showing at the conference?

 
Jehad Affoneh: In November, Project Clarity went Open Source. NG Conf will be the first conference that we’ve been to since then. We’re excited to showcase Project Clarity, especially the Angular components, and get feedback on the work we’ve been doing. Not only that, but we are looking forward to hearing back from people who have used Clarity. We always like hearing from our community and the Angular conference is a great opportunity to meet people and talk to them about their design system. We love Angular and we work regularly with the Angular team. We’re really excited to join the conference as members of the Angular community.

Is there anything specific the team looks to achieve at NG Conf?

At NG Conf, we want to communicate that VMware has been, and will continue to be, contributing members of the Angular community. As said, we’re really happy to be there as members. We want to share the work we’ve been doing with the Angular community, collect feedback, and share our plans for the future. We hope to meet and make some new community members – stop by our booth and meet our team and learn how you can use Clarity and contribute to its growth. Our team members will be attending several of the breakout sessions at the conference to both learn a little more about what’s going to happen with Angular moving forward, as well as be part of discussions with the Angular team.

Tell us a little more about the demos you’ll be showing at NG Conf.

We will be demonstrating our progress on Clarity as well as the work we’ve been doing. While there is no specific demo, we will be showcasing the overall Clarity design system. The larger VMware booth may participate in the NG Challenge at NG Conf, but the entry will be based on Clarity.

What’s the latest status on Clarity? Any releases of note? Feature Additions?

Since 11/15, when Clarity first debuted on github, we’ve had dozens of releases. Each one brings new changes to new components. Since going to open source, we’ve seen an uptick in contributors. We’ve also seen hundreds, if not thousands, of views to our website, as well as tens of thousands of users who have been both visiting and using Clarity. We’re very excited about the momentum of Clarity and look forward to seeing where this goes in the next few months. To keep up with Project Clarity, follow us on Twitter and visit our community blog. We post pretty regularly – we’re a very social bunch!

We’d love to hear more about the community engagement for the project.

We’ve seen a lot of engagements and contributions, as well as usage and applications built on top of Clarity since going to open source. As time progresses, we’ve seen more and more people come forward with contributions. That’s really exciting to us.

Any adoption stories to tell?

There have been a huge number of VMware applications and portfolio products that are either on Clarity, moving to Clarity, or have plans to move to Clarity – we’ve seen a huge adoption internally within VMware. Externally, we have been working with a number of different users. No specific adoption stories, but that’s something we’re working on to share within the next few weeks and months.

NG Conf takes place April 5th-7th in Salt Lake City, Utah. You can find more details here.