getting your blueprints accepted quicker in openstack

© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Swaminathan Vasudevan / HP Networking

Loïc Dachary / Upstream University

November 8th, 2013

© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.2

Free Software Cooperation works


Creating a Blueprint


What is a Blueprint

4

1. Have an Idea?

2. Capture your Idea.

3. Do some quick prototypes.

4. Publish your blueprint to the audience.


Have an Idea?


1.An idea can be as simple as an enhancement to an existing feature.

2.An idea can be as complex as a new feature or a plugin.

Idea


What problem does your idea solve? For example VPN as a Service for Neutron

Why does it matter for the Community?

ProblemOpenstack today does not have support for Virtual Private Networks (VPN) for the tenants as a Service in Neutron.

SolutionProvide an Advanced Service Plugin for VPN for the Tenant Network with a default VPN driver.

Capture your idea – Blueprint - Community


How is it related to Business Decisions???Enterprise customers need this feature as part of the Cloud offering and without this feature, it would be very difficult for Enterprise customers to use the public internet to access data in a unsecure way.

Why we choose VPN ?

It is a proven technology and currently used and widely accepted by all.

Capture your idea – Blueprint - Business


VPN Service PluginVPN as a Service for the Cloud Tenants and Service Providers.

Site-to-SiteProvides Secure Communication over the Public Internet to access the remote cloud resources.

Remote UsersAllows Remote Users and Remote Branch offices to be connected securely.

Blueprint – Use Cases (VPN Example)


Blueprint - Your Design/Proposal

After the Use Cases, the blueprint need to discuss our specific design.The design may include high level pictures showing the architecture for describing the solutionDataModel/Schema for the Plugin or extension that you are planning to implement.API Definition CLI DefinitionTest CasesDependencies if any


Blueprint Registration through Launchpad

1. Create a Launchpad Account.

2. Submit your blueprints through Launchpad for your respective projects.

3. Assign the blueprint for a particular milestone release.

4. Assign an Approver for the blueprint


Blueprint Follow-up1. Make sure that the community gets a chance to review your blueprint.

2. Send an email to the developers mailing list asking for interested developers to provide review comments on your blueprint.

3. Most of the times the developer community will review and post comments on the blueprints or send an email if anyone is interested.

4. If the blueprint is not reviewed, then bring to the notice of the specific groups during their weekly meetings.

5. The link provided here will give the details of the openstack meetings for a particular release cycle. https://wiki.openstack.org/wiki/Meetings

https://wiki.openstack.org/wiki/Meetings

https://wiki.openstack.org/wiki/Meetings


Blueprint Summit Session Registration1. Launchpad blueprint repository is the backlog and any blueprints

discussed in the design summit will get prioritized for the specific release cycle.

2. Launchpad Link https://launchpad.net/openstack

3. If your blueprint need to be prioritized and discussed in the upcoming design summits then you need to create a Summit session proposal for your blueprint and then link your original blueprint to the summit session.

4. Summit Session Link http://summit.openstack.org/

https://launchpad.net/openstack

http://summit.openstack.org/


Monitor Blueprint

1. Need to monitor the Blueprint status.

2. Blueprint status shows as Un-reviewed/Discussion/Refused or Approved/Pre-approved/Scheduled.

3. Watch for other Blueprints out there in the Launchpad that addresses the same problem that your blueprint addresses.


Start Meeting/Discussion with Peers

1. If there are more than one blueprints for the same feature then try to bring together all the blueprint owners and start the discussion with the group.

2. Organize regular meetings before the summit with the team if time permits.

3. Capture meeting logs and update the community on the meeting outcomes.

4. Make sure that you listen to everyone and get their review feedback. At the same time you also review other blueprints that are out there.

5. Finalize on the Use-Cases first.

6. Then finalize on the features.


Blueprint - Details

1. Blueprints need not be detailed.2. Blueprints that we submit are subject to change based on

the review feedback.3. So don’t take a long time to create and post a blueprint.4. The blueprints can be in a word document or it can be in a

Wiki format.5. OpenStack prefers the Wiki format for the final blueprint.6. Based on the effort of the work, the Blueprint will be

subdivided into multiple tasks and each task owner will be writing a detailed Wiki on those tasks.


Reaching Consensus with the Community

1. Be polite and gentle.2. Always listen and incorporate others feedback.3. Work as a team.4. Do not be harsh with others.5. Be patient, since you will receive positive and negative feedbacks.6. Align with what is required by the community rather than what is

required by you.7. Preference will be given to features that are desired by the

community if there is a choice.8. OpenStack always welcomes new people.


Blueprint Approval

1. Once the team agrees on the features and use cases, then identify the sub-team that would be implementing the feature.

2. Split the tasks and assign it to the respective owners.3. Each task owner then refines the blueprint and updates the

Wiki with the detailed information.4. If there is no respective blueprint in the launchpad to track

the task, it should be added and the task will be assigned to the respective owners.

5. The task owners will be held accountable for the tasks that they are implementing.


Technical Skills and Soft Skills

In order to get your blueprint approved you need to have Technical Skills and Soft Skills.

So far I did discuss about the Technical Skills and OpenStack working behavior.

But apart from the Technical Skills you have, some Soft Skills are required to be part of the OpenStack community and that is what I learned from the Upstream University.


Actual work : live and online training


First day : theory and simulation


Second day : planning and practice


Online mentoring : 1 h individual sessions


Companies, Universities, Individuals

getting your blueprints accepted quicker in openstack

Technology

blueprint status

blueprint registration

monitor blueprint

idea blueprint community

original blueprint

blueprint followup

idea blueprint businesshow

launchpad blueprint