• Like

Getting your Blueprints Accepted Quicker in OpenStack

  • 415 views
Uploaded on

Getting Your Blueprints Accepted Quicker in OpenStack: VPNaaS as an Example at the OpenStack Summit Hong Kong 2013 by Loic Dachary, Upstream University and Swaminathan Vasudevan, HP Networking

Getting Your Blueprints Accepted Quicker in OpenStack: VPNaaS as an Example at the OpenStack Summit Hong Kong 2013 by Loic Dachary, Upstream University and Swaminathan Vasudevan, HP Networking

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
415
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
13
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. 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 2 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 3. Creating a Blueprint 3 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 4. What is a Blueprint 1. Have an Idea? 2. Capture your Idea. 3. Do some quick prototypes. 4. Publish your blueprint to the audience. 4 4 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 5. Have an Idea? 5 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 6. 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. 6 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 7. Capture your idea – Blueprint - Community What problem does your idea solve? For example VPN as a Service for Neutron Why does it matter for the Community? Problem Openstack today does not have support for Virtual Private Networks (VPN) for the tenants as a Service in Neutron. Solution Provide an Advanced Service Plugin for VPN for the Tenant Network with a default VPN driver. 7 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 8. Capture your idea – Blueprint - Business 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. 8 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 9. Blueprint – Use Cases (VPN Example) VPN Service Plugin VPN as a Service for the Cloud Tenants and Service Providers. Site-to-Site Provides Secure Communication over the Public Internet to access the remote cloud resources. Remote Users Allows Remote Users and Remote Branch offices to be connected securely. 9 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 10. 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 solution DataModel/Schema for the Plugin or extension that you are planning to implement. API Definition CLI Definition Test Cases Dependencies if any 10 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 11. 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 11 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 12. Blueprint Follow-up 1. 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 12 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 13. Blueprint Summit Session Registration 1. 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/ 13 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 14. 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. 14 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 15. 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. 15 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 16. 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. 16 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 17. Reaching Consensus with the Community 1. 2. 3. 4. 5. 6. Be polite and gentle. Always listen and incorporate others feedback. Work as a team. Do not be harsh with others. Be patient, since you will receive positive and negative feedbacks. 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. 17 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 18. 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. 18 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 19. 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. 19 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 20. Actual work : live and online training 20 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 21. First day : theory and simulation 21 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 22. Second day : planning and practice 22 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 23. Online mentoring : 1 h individual sessions 23 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 24. Companies, Universities, Individuals 24 © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  • 25. Thank you Questions ? http://upstream-university.org/ © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.