satis egitimisatis egitimitengda.pro

Open@Blog

Discussion on the state of cloud computing and open source software that helps build, manage, and deliver everything-as-a-service.

  • Home
    Home This is where you can find all the blog posts throughout the site.
  • Categories
    Categories Displays a list of categories from this blog.
  • Tags
    Tags Displays a list of tags that has been used in the blog.
  • Bloggers
    Bloggers Search for your favorite blogger from this site.
  • Login

Historically, the computer industry has been impressed with big things.  In the early decades, the mainframes and supercomputers were all the rage.  Even as the technology began to shrink, big rollouts supplanted the big machines.  And now you can find powerful technology which easily fits in the palm of your hand -- but you've probably only heard of the brands which sell in huge numbers.

This industry likes big things.  But sometimes the greatest value comes from the smallest things.  That can certainly be said of Open Source conferences.

Good Things Really Do Come in Small Packages

I've spoken at several dozen Open Source conferences over the years.  I remember when LinuxWorld Conference and Expo was all the rage a decade ago.  It had thousands of attendees, gigantic booths, a huge amount of swag, and plenty of press coverage.  With all its lights and noise, that conference was something to behold.

But I don't find myself wishing I could revisit those days. Instead, I find myself enjoying the smaller, community-driven, regional conferences.  These conferences aren't large, aren't noisy, and don't come with mountains of swag to take home, but they provide attendees with something much more valuable: the equipment to succeed.

It varies from conference to conference, but most of these local conferences include two very important elements: excellent information and local networking. 

...
Hits: 1481
Rate this blog entry:
0
Continue reading Comments

[reposted from the Citrix blog]

The title of this post is a riff on the now famous quote by Mark Twain a.k.a. Samuel Clemens about the New York Journal’s confusion between him and at time his ailing cousin James Ross Clemens who was a continent away. The same thing happened recently with regards to two unrelated events. An organizational change here at Citrix and the perceived vitality of one of the technologies we help support, Apache CloudStack.

Recently we combined the Citrix Cloud Platforms Group and the Citrix Cloud Networking Group into one integrated unit called Citrix NCSP (Networking, Cloud & SP Group). We believe these changes will strengthen our position in the quickly evolving data center market.  Klaus Oestermann as the VP and GM of NCSP will lead the newly combined group. This will create a closer working relationship between the teams that develop our Citrix Cloud Platform (powered by Apache CloudStack), Citrix Netscaler and XenServer(built on Xen Project) and other related products.

Unfortunately some of the pundits in our industry are speculating as part of a recent  reorganization at Citrix (and the departure of some of our former colleagues to pursue other opportunities) that this is a sign that we are abandoning our commitment to Apache CloudStack and the project would die. That’s probably because they don’t exactly understand how the Apache Software Foundation(ASF) works and how Citrix supports them.

I suspect many of them don’t understand that despite the lack of fanfare that the ASF provides technologies that power most of the internet’s websites, a huge part of the Java ecosystem and much, much more. While the tech industry swoons over Big Data (a market that is estimated to reach $50 billion by 2017). They might be surprised to know that the Hadoop mapreduce technology that is the lynchpin for the movement is developed by a relatively small set of developers in the Apache Software Foundation. Or the the Apache httpd server that powers more websites on the internet than any other is maintained by a dedicated group of volunteers not a multi-billion dollar company.

...
Hits: 2045
Rate this blog entry:
0
Continue reading Comments

Open Source and Code Signing

Posted by on in Open Source

What is code signing

 

Code signing is the application of cryptographic hashes to code. Most people sign code in order to guarantee that no one has tampered with the code since publishing, and to explicitly be able to say that specific artifact originated somewhere. Most code signing relies on trusted third parties to effectively vouch for the identity of the signer. 

 

Open Source

 

Code signing isn’t really new, even in the open source world. Most Linux distributions have been signing their packages for years. But Linux distributions are fortunate in many ways. They own everything from the kernel to user land applications, and typically a user installs most if not all software via the distributions package repositories. This means you trust a code signing key shortly after or during installation for that distribution. Linux distribution users ‘trust’ packages that are signed by the same key as their installation medium. Most don’t check to verify that the signatures match what the project proclaims, but such verification is available. 

...
Hits: 1647
Rate this blog entry:
0
Continue reading Comments

With the Xen Project Hypervisor 4.4 having been released a few weeks ago, the project is starting the planning cycle for version 4.5 of the Hypervisor. So I thought it is worth walking you through how we manage releases.

Welcoming Oracle's Konrad Rzeszutek Wilk as Release Manager

But first I wanted to thank George Dunlap from Citrix for successfully managing the 4.3 and 4.4 releases of the Xen Project Hypervisor. The Release Manager role is a volunteer role open to Xen Project maintainers. George, has stepped down from his role recently to find more time for coding and help bootstrap the CentOS virtualization SIG.

Konrad Rzeszutek Wilk has volunteered to take on the role for the 4.5 release. A big welcome and Thank You!

Konrad is Software Development Manager at Oracle. His group's mission is to make Linux and Xen Project virtualization better and faster. As part of this work Konrad has been the maintainer of the Xen Project subsystem in Linux, Xen Project maintainer and now also Release Manager for the 4.5 release of the Xen Project Hypervisor. Konrad has been active in the Linux and Xen communities for more than 6 years and was instrumental in adding Xen Project support to the Linux Kernel.

How The Xen Project manages releases

As is the case for many open source projects, the Xen Project community does not maintain a committed roadmap as proprietary software vendors do. Instead, we strive to accurately track development for new releases, with a predictable release cadence for major releases and maintenance releases. We aim to release the Xen Project Hypervisor every 6-7 months: historically our release cadences ranged from 9 to 18 months. Introducing the Release Manager role was instrumental to getting us to shorter and a predictable release cadence.

...
Hits: 6804
Rate this blog entry:
Continue reading Comments

Quite a few years ago I made a rather nice living coding things up. Some were big projects used in regulated industries, and others a bit more mundane, but in all cases I tried to ensure confusion over what the point of the project was could be minimized. After all, the last thing I wanted was a prospective user or partner investing in something which wouldn't meet their needs.

Fast-forward to today, and as the XenServer evangelist I want to accomplish the same task, but scope is a bit broader. I want people to be using XenServer, and I want many tens of thousands of them doing so. By the same token, I also want those same users to know they are using XenServer, and not something else. After all, its equally bad if someone thinks they're using XenServer when they aren't, or are using something different when they are in fact using XenServer.

A perfect case in point is the confusion over what "Xen" and "XenServer" are. For years I've heard people who want XenServer referring to it as "Xen" and occasionally as "Xen Server". While many of those people aren't technical, and for them the distinction is largely irrelevant, the fact of the matter is the distinction does matter. For example, if someone is working on a project which they wish to integrate with XenServer, it does them no good to see references to "Xen" all over XenServer content, or to look at examples which reference "Xen"; even if the actual code is for XenServer and not "Xen". Even more significant is that, with the move of the "Xen" hypervisor to the Linux Foundation last year, what was once known as the "Xen" hypervisor has now become the Xen Project hypervisor.

All of which gets me to Apache CloudStack. Apache CloudStack is a wonderful solution for anyone looking to get a cloud up and running quickly, particularly those looking to have multiple hypervisors in their cloud and managed from a single console. Unfortunately, Apache CloudStack is also a perfect example of the problem I'm highlighting here. Within the UI, documentation and code, the term "Xen" and "XenServer" are used interchangeably, when in reality Apache CloudStack only supports XenServer; or more precisely XAPI based toolstacks for the Xen Project hypervisor. To resolve this problem, and to pave the way for the Xen Project hypervisor to become a full citizen of Apache CloudStack, I put forth a proposal to distinguish and disambiguate "Xen" and "XenServer". The design document can be found on the CloudStack wiki. To give an example of the cost of resolving these things after the fact; the initial patch consisted of over 17,000 lines, subsequent patches will be needed following extensive testing, all with the result of no new functionality. If you're interested in following the progress of this activity, please do so on the CloudStack mailing lists, and on the wiki.

The point I hope I'm making here is that when there is the potential for confusion, someone will eventually become confused. If you are working on something which references "Xen" or "XenServer", I hope you'll take a few minutes to see if you're using the right references and if not plan on clarifying things for your customers and users. To assist, please refer to this handy-dandy list:

  • "Xen" is a bare metal hypervisor which since April 2013 is a Linux Foundation Collaborative Project and has been renamed as the "Xen Project hypervisor". You can find more information about Xen Project at http://xenproject.org. Importantly, while "Xen" was the name Citrix used for the hypervisor, when "Xen" moved to the Linux Foundation, Citrix granted the Linux Foundation the limited rights to use the word "Xen" as part of the "Xen Project".
  • Citrix continues to use the "Xen" mark in connection with a variety of products such as XenApp and XenDesktop, so if you are working on a project with integration into other Citrix products, and are referring to them as "Xen", you risk further confusion with the hypervisor work occurring with both XenServer and the Xen Project.
  • XAPI, or XenAPI, is a toolstack for use with the Xen Project hypervisor and is a sub-project under Xen Project at the Linux Foundation. You can find more information about XAPI at http://xenproject.org/developers/teams/xapi.html
  • XenServer is a packaged virtualization solution from Citrix which in June 2013 was made completely open source. XenServer uses the Xen Project hypervisor and API support is provided via XAPI. Commercial support for XenServer is available from Citrix, and open source activities can be found on xenserver.org.
  • XCP, or Xen Cloud Platform, was a previous attempt at making XenServer open-source. With XenServer becoming open source in June of 2013, XCP development transitioned to XenServer.       
Hits: 17490
Rate this blog entry:
Comments

Open@Citrix

Citrix supports the open source community via developer support and evangeslism. We have a number of developers and evangelists that participate actively in the open source community in Apache Cloudstack, OpenDaylight, Xen Project and XenServer. We also conduct educational activities via the Build A Cloud events held all over the world. 

Connect