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!

Report: January month OpenStack meetup,Bangalore, India

In January we organized a meetup in Bangalore, India. http://www.meetup.com/Indian-OpenStack-User-Group/events/93144352/

The meetup was attended by over 75 people with different background start-up/students/researchers/MNC/Developers.

We started the meetup with general introductory session followed by few minutes session on OpenStack project and components.

Divakar Padiyar gave presentation on Cloud inventory, monitoring and alerting using HealthNMon

Nithya, Sarad and Suresh presented Introduction to Tempest along with nice demo.

Dinkar Sitaram and his students/faculty gave a presentation on Federated Keystone.

Chandan Dutta gave a presentation on OpenStack Quantum.

Anantha Padmanabhan gave presentation on VMware compute driver along with demo.

Slides are available  http://www.slideshare.net/openstackindia

Photos of the event are available  https://plus.google.com/photos/106314994124977332570/albums/5835386703034145825

Thanks to HP India for hosting/sponsoring the meetup/lunch  and  Bharat Ram, Srinivasa Acharya &  Himanshu Dwivedi for coordinating us on this.

 

Tags:

OpenStack Community Weekly Newsletter (Jan 11 – 18)

Highlights of the week

My first week at OpenStack

Victoria Martínez de la Cruz is one of the three interns working on OpenStack under the Outreach Program for Women (OPW –Anne Gentle shared some details about the program before.) She will be working on Tenant Deletion Workflow in the next months. This first blog post about OpenStack contains lots of good advice for any developer joining the community: a must read, for experienced developers, hiring managers and newcomers to this great community.

Ceilometer Grizzly 2 Milestone Available

The Ceilometer team is proud to announce the first synchronous milestone delivery with the OpenStack project. Grizzly-2 is also the last Folsom compatible version of Ceilometer as we are planning to introduce some breaking changes very soon in our trunk to enable a totally new set of features bringing Ceilometer beyond basic metering into monitoring and alerting.

How many people does one need to build a multi-region cloud?

Hui Cheng describes in details the StackLab project. Spearheaded by Sina, Intel, Gamewave, Xi’an Jiaotong University, South China University of Technology and others, it’s a non profit platform to try and test OpenStack. Sina’s OpenStack development team was responsible for the development, operations, and go online initially. More volunteers have joined the effort and are actively being recruited to get involved to this great career, which will accelerate OpenStack popularizing in China.

An Image Transfers Service For OpenStack

John Bresnahan makes the case for a new transfer service component in OpenStack. IaaS clouds must transfer VM images from the repositories in which they reside to compute nodes where they are booted. In the current state of OpenStack images download via HTTP to a nova-compute client speaking to the Glance image service. In the future proposed by John a transfers service would provide more predictable quality of service with horizontal scalability. Check his idea.

Ceilometer is looking for volunteers to take on unassigned blueprints

The team is about to start implementing the blueprints for the g3 milestone, there are few blueprints which still don’t have anyone assigned to them. If you are looking for something useful to code, head over to see the list of things that you could be working on. Remember that contributions during the Grizzly lifecycle will get you a free ticket to the OpenStack Summit.

Tips and tricks

Upcoming Events

Report from previous events

Other news

Welcome new contributors

Celebrating the first patches submitted this week by:

  • Toan Nguyen, Rackspace
  • Hans Lindgren, KTH
  • Flavio Percoco, Redhat
  • Michael J Fork, IBM
  • Sean Chen
  • Changbin Liu
  • Dan Florea, Cisco
  • Tony NIU
  • François Rossigneux, INRIA
  • Eric Peterson, HP
  • Sunil Thaha, 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:

OpenStack at FOSDEM’13

OpenStack will be showing a strong presence at FOSDEM 13, the largest gathering of free and open source developers in Europe.  There will be a number of talks in the Cloud devroom in the Chavanne auditorium on Sunday, February 3rd and in other places:

There will also be OpenStack mentions in various other talks during the day: Martyn Taylor should demonstrate OpenStack Horizon in conjunction with Aeolus Image Factory at 13:30, and Vangelis Koukis will present Synnefo, which provides OpenStack APIs, at 14:00.

On Saturday, Feb 2nd in room H.1309, at 11:50 James Page will talk aboutAutomating OpenStack Testing on Ubuntu, first hand experience from Ubuntu about testing on hardware every upstream commit. Hope to see many of you there.

Tags:

Summary and Review of the 2012 Openstack China Tour

In August 2012, the OpenStack Asia Pacific Technology Conference was successfully held in Beijing, Shanghai and the city, setting off public’s interest in OpenStack. On this basis, China OpenStack User Group(COSUG)  continues to work together with CSDN to further promote OpenStack in China, thus, a series of activities of the 8-city speech tour came into being.

The OpenStack Tour, which lasted three months, successfully ended in Wuhan on December 22.  This tour, which was organized by OpenStack user group (COSUG) and CSDN company, covered 8 big cities in China (Beijing, Shenzhen, Chengdu, Xi’an, Shanghai, Nanjing, Tianjin, Wuhan) Over 700 people participated in the on-site lectures and more than 30 people gave speeches. The event includes fantastic keynotes, which attracted more than 700 people to participate on site. The event provided a good exchange and communication platform for domestic developers and users of OpenStack, expanded the influence of the OpenStack community, and enhanced the OpenStack domestic level.

For the convenience of those who want to know more about this series of activities and OpenStack, we hereby write down the review and summary of the OpenStack China Tour activities. Hope you can further exchanges and communications between each other, therefore promote the development of OpenStack in China.

Content Guide:

1. 2012 Openstack China Tour Stop Cities

2. Enrollment and the Number of Participants

3. Lecturers

4. Review of Exciting Contents at the 8 Stops and Speech Downloading

5. Summary of Activities and Sharing of Operations Experience

1.      2012 Openstack China Tour Stop Cities

Initiated by Hui Cheng, the lead manager of China OpenStack community, and co-organized by   OpenStack User Group (COSUG) and CSDN, the 2012 OpenStack China Tour activities began on September 16, 2012, and ended on December 22, 2012, respectively covering Beijing, Shenzhen, Chengdu, Xi’an, Shanghai, Nanjing, Tianjin and Wuhan.

2.       Enrollment and the Number of Participants

 The recruitment of participants took full advantage of CSDN, who has a huge amount of developer members. The participants of each activity are really interested in this technology. Venues were sponsored by the guests involved in the activities. Among the eight venues, only Shenzhen was under AA system, and the others were lent for free by local volunteers. The total enrollment of the 8 events is1060 and the actual number of participants is 710.

3.      Lectures

The theme of which is around OpenStack, this series of activities convened companies and institutions principally engaged. The lecturers were front-line OpenStack engineers, OpenStack code contributors, developers, experienced users, etc. The total number of lecturers is 31, 7 at Beijing stop, 6 at Shenzhen stop, 6 at Chengdu stop, 4 at Xi’an stop, 7 at Shanghai stop, 7 at Nanjing stop, 5 at Tianjin stop and 5 at Wuhan stop. As the initiator of the 2012 OpenStack Tour, Hui Cheng attended the events held in six cities. Rongze Zhu, Storage Engineer of Sina Cloud Computing, also gave speeches at multiple stops.

Introduction to lectures and their topics

 Introduction to lectures and their topics

4.      Review of Exciting Contents at the 8 Stops

1)      Beijing Stop

OpenStack China Tour (Beijing Stop) was held in workplace of Shanda Innovations. Core contribution engineers from Intel, Sina, IBM, Gamewave etc. made presentations. Over 150 engineers attended this activity on-site. And more than half a hundred of engineers watched the whole meeting live through WebEx.

As the most influential OpenStack senior engineer and early evangelist in China, Hui Cheng gave a deep insight about the open ecosystem of OpenStack, and why OpenStack becomes so successful. Hui shared the latest OpenStack events happened both at home and abroad.

“Sina, Intel, IBM, Baidu, Netease, HiSoft, China Standard Software, Gamewave Ltd., Shanghai Jiaotong University has become the first wave of OpenStack players in China” said Hui Cheng, “They have already deployed OpenStack to their production or testing environment, and some of them is also the active corporate contributor in OpenStack projects. For example, Sina has already contributed more than 100 patches in the OpenStack Folsom release, and definitely will have more in Grizzly.”

In addition, Hui Cheng said, “Sina will join hands with some companies, such as Intel, IBM, and other major Chinese corporate contributors, to unite the R & D resources, and jointly develop for some project blueprint, thereby to enlarge the contribution from China.

Topics:

Topic 1: OpenStack and OpenStack Foundation

Topic 2: Brief Introduction to OpenStack Virtualization Technology

Topic 3: Introduction to Quantum, its structure and practice

Topic 4: OpenStack block Device Storage Services

Topic 5: Deploy OpenStack with Chef

Topic 6: Explanation of Keystone

Topic 7: Thinking of Cloud Computing

Detailed Report on Beijing Stop

http://www.openstack.org/blog/2012/09/openstack-china-tour-beijing/

Speech materials of Beijing Stop Downloading:

http://download.csdn.net/download/baozi0/4574729

 Video Downloading:

http://v.youku.com/v_show/id_XNDUxNTE1Nzc2.html

2)      Shenzhen Stop

The Shenzhen Stop Activity was held in 3Wcoffee. It was the first time that OpenStack came to Southern China. This event attracted over 80 on-site attendees. Most of them were Cloud specialists, IT engineers, as well as OpenStack users from Canton, Shenzhen, Hong Kong and Hangzhou etc.

Topics:

Topic 1: Development Practice of Building Public Cloud Platform Based on OpenStack

Topic 2: OpenStack in Hong Kong

Topic 3: Swift Architecture and Practice

Topic 4: OpenStack Block Device Storage Services Cinder

Topic 5: Juju – Make Your Life Easier in the Cloud

Issue 6: OpenStack – The Best Private Cloud Infrastructure for Enterprises

Detailed Report on Shenzhen Stop Activity:

http://www.openstack.org/blog/2012/09/openstack-china-tour-2-shenzhen/

Speech Materials of Shenzhen Stop Downloading:

http://www.csdn.net/article/2012-09-22/2810244-OpenStack_china_tour_Shenzhen

Video Downloading:

http://download.csdn.net/detail/baozi0/4588357

3)      Chengdu Stop

The Chengdu stop event was held at e Coffee in Tianfu Software Park in Chengdu. Hui Cheng, community manager of China OpenStack User Group (COSUG), led engineers from Redhat, Ubuntu, Sina and IBM to this event. All of them made wonderful presentations, which attracted about 100 stackers to participate in this activity.


Topics:

Topic 1: StackLab: An Open OpenStack Lab

Topic2: Introduction for libvirt architecture and APIs

Topic 3: Juju – Make Your Life Easier in the Cloud

Topic4: Adoption OpenStorage with Openstack

Topic 5: Swift Architecture and Practice

Topic 6: Introduction to Quantum, its structure and practice

Detailed Report on Chengdu Stop Activity:

http://freedomhui.com/2012/11/chian-openstack-tour-chengdu/

Speech Materials of Chengdu Stop Downloading:

http://download.csdn.net/detail/baozi0/4699418
http://download.csdn.net/detail/baozi0/4700507

4)      Xi’an Stop

The Xi’an stop event was held at Qing Feng Plaza, Software Park in Xi’an. Engineers from RedHat, Sina and Stackform attended this event. All of them made wonderful presentations, which attracted about 110 stackers to participate in this activity.

Topics:

Topic 1: Practice of OpenStack Public Cloud

Topic 2: The OpenSource OpenStack+OpenShift

Topic 3: OpenStack Block Device Storage Services Cinder

Topic 4: Incubation Cloud Management Platform Based on OpenStack

Detailed Report on Xi’an Stop Activity:

http://freedomhui.com/2012/11/china-openstack-tour-xian/

5)      Shanghai Stop

The Shanghai Stop event was held in an innovation workshop. Engineers from Sina, Intel, trystack.cn, and Dell gave wonderful speeches. Around 40 OpenStack enthusiasts attended this event on-site.

Topics:

Topic 1: Practice of OpenStack Public Cloud

Topic 2: Practice of OpenStack Public Cloud

Topic 3: Swift Infrastructure and its Key Technologies

Topic 4: Cinder Project Status and New Feature for Grizzly

Topic 5: Swift Performance Measurement and Tuning

Topic 6: Internal process of Quantum

Topic 7: Nova and Virtual Machine Management

Detailed Report on Shanghai Stop Activity:

http://adali.iteye.com/blog/1730445

Speech Materials of Shanghai Stop Downloading:

http://openstack.group.iteye.com/group/topic/35090

6)      Nanjing Stop

The Nanjing Stop event was held in Gulou Campus of Nanjing University. As one of the founders of China OpenStack User Group (COSUG), Yujie Du gave a speech at the event. Cloud computing architect from 360buy, Manager of NEC Development Department, OpenStack community developers, Ubuntu developers and technical pre-research engineer from ZTE the Openstack gave wonderful speeches. The number of on-site audience was more than 70.

Topics:

Topic 1: Introduction to OpenStack Foundation and the Community

Topic 2: Realization of 360buy ELB

Topic 3: Applicatios Based on OpenStack and Openflow/SDN

Topic 4: Internal Process of Quantum

Topic 5: OpenStack+OpenShift

Topic 6: Juju – Make Your Life Easier in the Cloud

Topic 7: OpenStack Operational Needs and Practice in Telecommunications Industry

Detailed Report on Nanjing Stop Activity:

http://www.csdn.net/article/2012-11-29/2812349-OpenStack_china_tour_nanjing

Speech Materials Downloading:

 http://download.csdn.net/detail/adela_09/4825545

7)      Tianjin Stop

The Tianjin Stop event was held in the Tianjin Economic and Technological Development Zone. Representatives from the four major open source platforms (OpenStack, CloudStack, Eucalyptus, OpenNebula) got together and explored the future development of OpenStack.

Topics:

Topic 1: Commercial Thinking on OpenStack

Topic 2: Experience Sharing of Developing Public Cloud Solutions Based on OpenStack

Topic 3: The development of CloudStack and its China Community

Topic 4: Experience Sharing of Developing and Infrastructure Analysis of OpenNebula

Topic 5: Introduction to Eucalyptus Components

Topic 6: Panel

In the panel forum, Hui Cheng (OpenStack user group (COSUG) Administrator), Xuehui Li (CloudStack Committer), Qingye Jiang (Eucalyptus Account Director), China cloud Junwei Liu (computing researcher of Academy of Telecommunications Research) launched a discussion. Each of them introduced their most successful open-source platform deployments.

Detailed Report on Tianjin Stop Activity:

http://www.csdn.net/article/2012-12-14/2812845-the_DNA_of_open_IaaS

Speech Materials Dowloading:

http://download.csdn.net/detail/baozi0/4868518 

http://www.youku.com/playlist_show/id_18680644.html

8)      Wuhan Stop

The Wuhan Stop event was held in Huazhong University of Science and Technology. Experts from Sina, Zhongda Huanyu, and OS-Easy gave speeches on the following topics.

Topic 1: The Road of Cloud Computing Adoption—OpenStack Open Source Cloud Platform

Topic 2: Deploy and Manage OpenStack on Crowbar

Topic 3: Practice of Build Server virtualization Based on OpenStack

 Topic 4: Integration Practice of OpenStack and Hadoop

Detailed Report on Wuhan Stop Activity:

http://adali.iteye.com/blog/1753943

  1. Summary of Activities and Sharing of Operations Experience

The activities of the the “OpenStack line” is a community collaboration Technical Tour of exploration. In the case of commercial sponsorship, community activities are often faced with three questions: Lecturer, venue and participants. The event lecturers are volunteers, travel expenses own burden, activities to attract so much lecturer to join, thanks to OpenStack have accumulated under the core members of the user group in China more than a year operations. Eight venues of the city, only Shenzhen is using the AA system, others are lent free of charge by local volunteers. Recruitment of participants take full advantage of the CSDN advantage of the huge amount of developers Member, participants of each event are really this crowd interested in technology.

The event has accumulated a lot of experience.

How to push offline activities to online. Offline activities have pros and cons. Interactivity is the advantage. Face-to-face communication is the most efficient. In the beginning of promoting technologies such communication is really needed. The disadvantage is that such communications are costy.  In order to make offline activities as fruitful and influential as possible, collecting materials accessible online is need as much as possible, such as speech scripts, photos, video, and reports.

On-site activities. Organizers were multitaskers, who were responsible for registering, contacting lectures, hosting meetings, reminding, taking photo, several roles to manage the conference attendance, Lecturer Contact presided over the meeting, reporting, etc. It would be better if some people are willing to take some tasks, if they don’t want, the tasks should be in order. Contacting lectures and controlling time are the most important, followed by collecting materials. Here is a tip. Here is a tip. You’d better collect speech materials as soon as the conference ends. Otherwise, you have to ask lectures email you their speech materials. If this is the case, you have to wait for a long time. So the priority after the activity is to post the materials collected online.

Meeting Application Control. To organize an offline activity, two extremes should be avoided. If few people, the scene looks empty. If too many people, it would be crowded. Attendees would feel uncomfortable. At the stage of releasing and promoting the activity,     organizers should know how to make full use of the accessible resources. Promote from the core to the periphery. When the number of applicants reaches the expected goal, you do not have to re-accumulate marketing resources. In accordance with the experience of organizing community activities, to have 50% applicants attend the activity is reasonable.

Location. Previous community activities helped bring some free venue, which can be reused .For the venue provider, supporting community activities is a good way to improve the company’s reputation. And if the activities are responding the company’s business, this is like requesting experts to deliver free trainings for employees. Software Parks and software base in some cities can also be sponsors. But in practice, free venues were gotten by using personal relationships, such as friendship, colleagueship, former colleagueship, and so on.

If you can’t find a suitable venue by using some existing resources, you can seek help in mail group. Such as sending requests in COSUG mail group. But be sure to write clearly all your needs in one email. Otherwise, your frequent emails would disturb others. Internet search  is also a good way. For instace, by googling keywords, “**community”, “community activities” to find related persons in charge. Generally, these people are active online. You can be linked to these people through various activities pages and microblogging. These people usually have some resources at the local, and are very kind.

After visiting so many venues looking down, we find they all have advantages and disadvantages. Offices in companies have good conditions, but they are usually not air-conditioned on weekends, sometimes, you may run into blackout. In addition, security measures are strict and you have to registration at the door. Cafes possess comfortable environment, but they charge and the space is limited. Big university classrooms are wonderful. But for foreign participants who are unfamiliar with the campus, they have to waste some seeking the specific classroom which is usually not identifed on a map. Software parks and software bases are extremely good, but you’d have to hold the activity there during the working day. Because on weekends, there are people in such work places far away from the downtown.

Like lectures, alternative venues are also needed. Lots of lectures and audience will gather at one specific place at the same time. If the activity is cancelled due to venue problems, many people will be sad and disappointed, what’s worse, once this kind of unreliability spreads out , it would be more difficult to gather people next time.

Concern about participants. Because community activities are frequently held on weekends, Participants are more enthusiastic than other people will be more enthusiasm. They are the resource of volunteers. Hosts and organizers should communicate with these potential volunteers at the scene. Reunions after the activity are a good way.

Volunteers. Lots of volunteers are needed community activities. Some organizers think the recruitment of volunteers is very simple, just listing tasks, and waiting for claim. However, some organizers don’t think this is easy. This is a matter of opinion. Actually, many volunteers claim voluntary work by themselves. So clearly write down organizers’ email addresses or phone number on the propaganda or in email. This allows those who are interested to easily find you. Another method is to collect. List stuffs and tasks that need volunteers’ assistance in email or microblog. Then people would apply. Most volunteers are students, some are those who are very active in community.

Chinese Version of this post: http://blog.csdn.net/ichbinwasser/article/details/8447542(Author: CSDN)

Tags: