TryStack.cn Community 2nd Meetup – 19th February 2013

In the first meetup we talked about what’s going on with China OpenStack User Group(COSUG), and shared the latest experience for Quantum with community members. This time we will tell you how to master OpenStack in 2 hours for the beginners. There were about 200 registers, and about 100 people attended this event through on-site and online live.

Trystack series

This is the first public lecture series of trystack.cn. First, we gave a Brief introduction about OpenStack, and talked about why OpenStack is so popular in China.

trystack series

Then a introductory way was provided to the beginners, using devstack scripts. Later in this lecture, I explained how to use stack.sh with some Tips & Tricks.

After a short introduction about trystack.cn, we enter into Hands-on Lab unit. There were some demo and show-off on trystack website to help the newbie to master OpenStack.

At last but not least, thanks to our contributors and partners/sponsors!  The next activity are looking forward to your participation. The slides for trystack meetup are all on slideshare, please pay close attention to @COSUG and @trystack for more information. If you have any questions and feedback, please contact us [email protected].

Tags:

OpenStack Community Weekly Newsletter (Feb 8 – 15)

Highlights of the week

Important CLA changes coming in 10 days

Starting on February 24, 2013 all contributors MUST review and agree to the new OpenStack Individual Contributor License Agreement and provide updated contact information at https://review.openstack.org/#/settings/agreements. On that day the Gerrit interface will be changing to present the new CLA text referring to the OpenStack Foundation, and will prompt you to agree to it there. Any previous agreement with OpenStack LLC will be marked expired at that time. The text of the new agreement is available for your convenience (just changes “LLC” to “Foundation” and corrects a few typographical errors). You must also sign up for an OpenStack Foundation Individual Membership with the same E-mail address as used for your Gerrit contact information: http://openstack.org/register/.

OpenStack Object Storage (aka Swift) for new contributors

As a developer, jumping into a mature codebase can be somewhat daunting. How is the code structured? What is the request flow? What’s the process for getting my changes contributed upstream? Find answers to these questions on this post by SwiftStack.

Evolution of the incubation process

The Technical Committee approved a set of changes to the incubation process, the process through which a project becomes part of the co-ordinated, integrated OpenStack release. One of the visible change is the switch from using the term “Core projects” to “Integrated”.

Upstream University at the OpenStack summit

Upstream University is organizing a session in advance of the next OpenStack summit, in Portland. If you can fly in two days ahead of the event to spend the weekend improving your OpenStack contribution skills, please consider submitting an application to attend the workshop.

Python trademark at risk in Europe: Python Foundation needs your help

For anyone who works in a company that has an office in a EU Community member state, the Python Software Foundation needs your help. There is a company in the UK that is trying to trademark the use of the term “Python” for all software, services, servers… pretty much anything having to do with a computer. The PSF is asking a letter on company letterhead to forward to their EU counsel. More details on PSF News.

Report of Openstack project on SF State University campus

Two students (Brandon Lai and Pascal Schuele) under supervision of prof. Sameer Verma worked on exploring the cloud computing space in Fall 2012. They built a demo/prototype of a private cloud platform on campus and presented at the end of the semester. Prof. Verma hopes to continue to expand this project in Spring 2013.

Security Advisories

Tips and Tricks

Upcoming Events

Other News

Welcome New Contributors

Celebrating the first patches submitted this week by:

  • Tim Potter, HP
  • Jean-Baptiste RANSY, Alyseo
  • Nicholas Kuechler
  • Adalberto Medeiros, IBM

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

Tags:

OpenStack Community Weekly Newsletter (Feb 1 – 8)

Highlights of the week

Best way to brag about contributing to Grizzly?

Contributors to OpenStack Folsom received a nice patch to stick on something you carry every day like a backpack or your favorite sweater. Would you like to get a patch for Grizzly, too? Would you rather get something else to brag about your ‘Contributor’ status? Let us know your preferences.

Packstack: Openstack Install tool

There is a new tool that installs Openstack either on bare metal or Vms: it can be found on github under the fedora-openstack organization. Packstack is currently in its first ages and still under heavy development but, it’s already capable of installing, customize some parameters and distribute most of the Openstack modules on a single server or several as well. It currently supports Red Hat based distros but there’s space for more.

Testing (OpenStack)

Anita Kuno, one of our awesome intern of OPW program, tells the tales common to new developers learning about OpenStack developer’s community. In this new installation she tells us how she had to run some tests in /opt/stack/nova and every command failed. Why? She didn’t know. But now she does.

Cloud Prizefight: OpenStack vs. VMware

There have been many discussions in the cloud landscape comparing VMware and OpenStack. In fact, it’s one of the most popular topics among those thinking about using OpenStack. Mirantis’ Lee Xie judged the two in the following categories: design, features, use cases, and value. The categories are scored on a 10-point scale and then tallied to determine the winner.

In a nutshell: How Does OpenStack work?

Victoria Martínez de la Cruz, another awesome intern of OPW program, uses pictures and words to explain in a blog post how OpenStack works.

Security Advisories

Tips and Tricks

Upcoming Events

Reports From Past Events

Other News

Welcome New Contributors

Celebrating the first patches submitted this week by:

  • Kurt Martin, HP
  • Svetlana Shturm, Mirantis
  • Mitsuhiko Yamazaki, NEC
  • Andrea Frittoli, HP
  • James Morgan, Rackspace
  • Jesse Pretorius
  • Nathan Reller, JHU APL
  • Rami Vaknin, Redhat

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

Tags:

TryStack.cn 2013 first meetup

Last week we organized the first meetup (Intermediate) in 2013 for trystack.cn in China. The meetup was attended by about 100 people with developers and operators that want to understand how to make OpenStack production ready for their organization.

The topic was about OpenStack What’s going on in China. During the event, the attendants had a chance to listen to some introduction about international community, according to the speacker’s experiences at OSCON2012 and OpenStack Summit in San Diegon last year. And then it introduces the current work in trystack.cn, such as work together with VMWare China team on CloudFoundry region with Folsom, the latest to experience Quantum.

Trystack.cn was announced in San Diego during the OpenStack Summit. Not only provide virtual machine for the users, but a non-profit community projects for the stackers to experience the lastest OpenStack features.It is the community who should, in the main, determine how to use the resources, and how to feedback to the community. So basis on a lot of COSUG activities last year, it feels appropriate, as the year draws to a close, a time when we look both back and forward at the start of a new year.

IMG_1049Trystack.cn meetup

The slides for this meetup are on slideshare and you may be interested in reading more on this interview with Dell. The TryStack.cn team is on Google Groups, Slideshare, Weibo:  @COSUG (China OpenStack User Group ) and @trystack. Contributions and feedback are welcom: Join the fun !

Tags:

OpenStack Community Weekly Newsletter (Jan 25 – Feb 1)

Highlights of the week

“H” stands for Havana

The polls closed, Havana will be the code name for the OpenStack release following Grizzly.

Contributing to OpenStack

Rackspace’s Iccha Sethi and Alex Meade conducted a workshop on Contributing to OpenStack. Look at Iccha’s presentation on her blog.

Quota Project: An effective way to manage the usage of your Swift-based storage cloud

Quota is a production-ready project that is mainly used for controlling the usage of account and containers in OpenStack Swift. The Zmanda team talks about Swift Quota which has been used in StackLab – a production public cloud for users to try out.

OpenStack 2012.2.3 released

In the time since the Folsom release, the maintainer of OpenStack stable branch have been busy selectively back-porting bugfixes to the stable/folsom branch according to our “safe source of high-impact fixes” criteria. These releases are bugfix updates to Folsom and are intended to be relatively risk free with no intentional regressions or API changes. Read the full Release Notes.

Access OpenStack Swift as an FTP/SFTP service

ftp-cloudfs is a proxy service that can be used to access to the object storage with any regular FTP client. The project is mature now and it’s in production at Memset and other cloud storage providers. Sftp-cloudfs offers similar abstraction but for the SFTP. The code is on github for both projects https://github.com/chmouel/ftp-cloudfs and https://github.com/Memset/sftpcloudfs

Looking for active reviewers — and inclusion in QA-core

As the OpenStack projects grow, so does Tempest. While the team has been successful recently in improving the runtime of Tempest and getting full test suite runs gating other projects, the number of new code submissions to Tempest has exploded recently as more contributors find their way to Tempest. What this means is that the team needs more people that do reviews.

Security Advisories

Tips and tricks

Upcoming Events

Other news

Welcome new contributors

Celebrating the first patches submitted this week by:

  • Paul Michali, Cisco
  • Motonobu Ichimura
  • umamohan, HP
  • Roman Prykhodchenko, Mirantis

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

OpenStack Community Weekly Newsletter (Jan 18 – 25)

Highlights of the week

Project Incubation Process Update is Underway

Alan Clark, Chairman of the Board, wrote about the effort to improve the existing open source incubation process for OpenStack. This is one of the most important processes kickstarted by the OpenStack Foundation whose objective is to help ensure that projects receive the focus, visibility and resources needed to be successful via a fair, equitable and open process.

Introducing the User Committee

Speaking of important processes, here is another one you should pay attention to: the OpenStack User Committee whose role is to represent the needs of the diverse range of OpenStack users. For those of you who would like to help define this committee, please look at the points to review document and post your thoughts to the OpenStack foundation mailing list.

Debugging OpenStack with pycharm and pydevd

The story of a conversion, that of John Bresnahan from being a strictly vi user, developing C code and debugging with gdb, to an avid user of pycharm. This is a story of lost productivity of a once Luddite converted to IDE and of how he got to appreciate remote debugging via pydevd.

Technical Committee & Grizzly Update

While we wait for the final release of OpenStack Grizzly, here is a teaser of what’s coming up, with other updates from the OpenStack Technical Committee. Read it together with the Motion on Technical Committee membership for Spring 2013 session.

Let’s Get this Started!

And ‘this’ is the Outreach Program for Women, coordinated by GNOME, with OpenStack as one of ten participating organizations: we’ve added a few more ladies to the OpenStack contributors starting line this month.

We are seeking sponsorships to bring all of them to the OpenStack Summit in Portland in April. If you are interested please contact Anne Gentle at [email protected]. For a few thousand dollars, we can learn from them as much as they are learning from us. A great opportunity for some great interns!

On-disk encryption prototype for OpenStack Swift

A few months ago, Mirantis engineers described the design of on-disk per-user encryption of objects in Swift. They released a first working prototype of this feature. It’s still very basic at the moment, but most of its components are pluggable and can be enhanced or replaced with more advanced versions. Code on Github.

Tips and tricks

Upcoming Events

Report from previous events

Other news

Welcome new contributors

Celebrating the first patches submitted this week by:

  • Wenhao Xu
  • gtt116
  • Spencer Krum, Portland State University
  • Mat Grove
  • Burt Holzman, Fermilab
  • Chet Burgess, Metacloud

The weekly newsletter is a way for the community to learn about all the various activities occurring on a weekly basis. If you would like to add content to a weekly update or have an idea about this newsletter, please leave a comment.

Tags:

Project Incubation Process Update is Underway

If you take a moment to view the different projects, committees and work groups that are currently underway within the OpenStack project, 2013 is looking to be a very exciting year for cloud computing.  I could easily write an entire dissertation about the accomplishments the community will make this year now that the OpenStack Foundation is launched and the Technical Committee (TC) and OpenStack Board are formed. For this update, I’ll spare you the lengthy dissertation and focus on our effort to improve the existing open source incubation process for OpenStack. For ease, let’s call the incubation process update the IncUp effort.

The incubation process provides new projects the oversight, guidance and time needed to grow and mature.  The goal is to assure projects meet a high standard of usefulness and quality as they mature and become an integral part of OpenStack. The current process has served OpenStack well. Through that process the project has developed several key technologies that are core to OpenStack.

I read a funny quote  attributed to Mark Twain, “A man who carries a cat by the tail learns something  he can learn in no other way.”   The TC has done a wonderful job with the current incubation process, with lessons learned and experience gained. With formally outlined roles and responsibilities by the Foundation bylaws the TC and Board have increased responsibility to ensure the incubation process is a success.

The goal of the OpenStack Foundation is to serve developers, users, and the entire ecosystem by providing a set of shared resources to grow the footprint of public and private OpenStack clouds, enable technology vendors targeting the platform and assist developers in producing the best cloud software in the industry.

To better meet this challenge, the Technical Committee (TC) and OpenStack Board have kicked off the IncUp effort to update the current incubator process.  The effort is significant to all of us within the community because it’s a fundamental part of how a project’s destiny is determined.  A clearly defined incubation process influences the way we work together, facilitates growth, and ensures success through fair equitable and open processes.

Gandhi said, “be the change that you wish to see in the world.” Which profoundly articulates how much of IncUp we’ve already accomplished through our current state of “being.” The launch of the Foundation established an independent, vendor neutral, secure and safe environment for OpenStack technologies to grow.  Today, members of the board and the technical committee work together for the proper advancement of OpenStack technologies. And support from our members, sponsors, community and dedicated resources foretell the many projects underway within the OpenStack Foundation are already positioned to succeed.

Over the past several weeks, the IncUp committee has spent much time ensuring we understand the current incubation process and the issues at hand. Many questions were raised and we’re listening closely to feedback from project leads. The information we’re collecting is helping us rapidly paint the improved process.  Once that step is complete we will quickly draft the updated process, conduct reviews and prepare to roll out the updates.

Much of the fun of open source is the feeling of being part of and contributing to a recognized, successful project.  The continued purpose of the IncUp effort is to help ensure that projects receive the focus, visibility and resources needed to be successful via a fair, equitable and open process.  A process that ensures open source projects support the mission of the Foundation and the purpose of OpenStack.

I agree with Mark Collier when he said one day cloud computing will power our global economy.  I believe this can only be accomplished with the mindset to make technology collaborative, affordable and available to all. OpenStack is an exciting place to be for 2013.  The IncUp effort is one of many great things happening this year. Be sure to join a project, committee or work group to be a part of the future of cloud computing.

Introducing the User Committee

As the number of production OpenStack deployments increase and more ecosystem partners add support for OpenStack clouds, it becomes increasingly important that the communities building services around OpenStack guide and influence the product evolution.

When the OpenStack Foundation was launched in 2012, there were two initial structures created. The management board provides strategic and financial oversight of Foundation resources and staff. The technical committee defines and stewards the technical direction of OpenStack software development. We are now establishing the user committee whose role is to represent the needs of the diverse range of OpenStack users.

The user committee mission is to

  • Consolidate user requirements and present these to the management board and technical committee
  • Provide guidance for the development teams where user feedback is requested
  • Track OpenStack deployments and usage, helping to share user stories and experiences
  • Work with the user groups worldwide to keep the OpenStack community vibrant and informed

The structure of the user committee is currently being defined. Tim Bell, Ryan Lane and J-C Martin have been nominated by the management board and technical committee to work with the community and determine the by-laws and scope. This process is ongoing through the foundation mailing list and points to review document. Amongst the areas of discussion are the definition and representation model of the wide spectrum of users in different industry segments ranging from end-users submitting work to an OpenStack cloud through ecosystem partners using the APIs to provide additional services to those deploying and operating clouds in production. It is also planned to expand the committee further to cover both industry segments and user group representation along with running a user survey with the goal to present the results at the next summit.

For those of you who would like to help, please look at the points to review document and post your thoughts to the OpenStack foundation mailing list.

Technical Committee & Grizzly Update

The OpenStack development teams continue to make progress in many areas. We recently published the grizzly-2 development milestone. It marks the middle of the “Grizzly” development cycle, which will end on April 4. So far 99 feature blueprints have been completed, and 113 more are still likely to be included before our feature freeze date on February 19th. This will mean nearly 200 improvements by the time the final release arrives.

Some changes are very visible, like the introduction of new versions of APIs and support for new networking, storage and authentication backends. Also, this release includes the much-anticipated work on Compute Cells that makes it easier to deploy and manage OpenStack clouds at very large scale. Some other changes are less visible, but as important, like the creation of common libraries to reduce technical debt and minimize duplication of code between projects.

Our development infrastructure, handling about 2000 commits per month, continues to improve. It now runs even more unit and integration tests before accepting new code, while reducing the overall time it takes to run them!

The Technical Committee has begun meeting regularly and working on a number of items. It decided to accept into incubation the Ceilometer and Heat projects, adopted new policies on 3rd-party API and Python support, and is participating in the joint committee working on defining the future of Incubation and Core with the Board of Directors.

Let’s Get this Started!

I went to college in Indianapolis as one of the fine Butler Bulldogs. Each spring the Indy 500 car race is a celebrated event. On Labor Day weekend, the call for the engines to start is made by stating “Gentlemen, start your engines!” When female drivers are competing, the call becomes “Lady and Gentlemen…” or “Ladies and Gentlemen, start your engines!” I’m pleased to say that we’ve added a few more ladies to the OpenStack contributors starting line this month. In December we got to know each other through a Google Hangout, here we are waving and smiling for the camera.

The Outreach Program for Women is coordinated by GNOME and OpenStack is one of ten participating organizations. The OpenStack Foundation, Rackspace, and RedHat sponsored three interns, and after our careful selection process, we chose these three fine candidates and matched them with the mentors listed below:
Laura Alves da Quinta (http://ladquin.dreamwidth.org/), Buenos Aires, Argentina – Documentation – Anne Gentle
Anita Kuno (http://anteaya.info/), Haliburton, Ontario, Canada – Python Clients – Iccha Sethi
Victoria Martínez de la Cruz (http://vmartinezdelacruz.com/), Bahía Blanca, Argentina – Horizon’s Workflows – Julie Pichon

We are seeking sponsorships to bring all of them to the OpenStack Summit in Portland in April. If you are interested please contact Anne Gentle at [email protected]. For a few thousand dollars, we can learn from them as much as they are learning from us. A great opportunity for some great interns!