Jump to: navigation, search

Governance/ElectionsSpring2012/Vishvananda Ishaya

Vish Ishaya

Template:Http://farm6.staticflickr.com/5122/5373303391 189ab48488.jpg

I'm the incumbent candidate for Project Technical Lead to Nova

OpenStack bio

I was one of the original authors of nova when it was still part of the NASA Nebula project. OpenStack has been my life for the last 2 years. I was elected to the PPB during the first election, and then elected as the PTL for Nova. I have been serving as the PTL for the last year. There is a huge amount of work involved in being a PTL for such a large project, including managing blueprints and scheduling, bug triaging, mailing list debates, working with partner companies, and answering mailing list questions. In addition to these managerial tasks, I work on all aspects of the nova code base, and spend lots of time answering questions on IRC and launchpad.

Questions

I'm not running for a PPB seat specifically, but so much of what I do involves OpenStack as a whole, I decided to answer both sets of questions below.

1a. Since the last elections, what areas have you focused on and what contributions have you made in order to improve OpenStack as a whole?

I've been spending time making sure that nova is integrated well with the other projects, especially focusing on keystone.

Devstack contributions: https://review.openstack.org/#q,owner:+vishvananda%2540gmail.com+project:openstack-dev/devstack,n,z Keystone contributions: https://review.openstack.org/#q,owner:+vishvananda%2540gmail.com+project:openstack/keystone,n,z https://review.openstack.org/#q,owner:+vishvananda%2540gmail.com+project:openstack/python-keystoneclient,n,z

I've also been working closely with Dan on Quantum integration and a plan for the openstack networking api.

In addition I've been working with various groups on elevating nova-volumes into its own project.

1b. Since the last elections, what areas have you focused on and what contributions have you made in order to improve your project?

I have directly implemented a number of blueprints and bugfixes. https://review.openstack.org/#q,owner:+vishvananda%2540gmail.com+project:openstack/nova+status:merged,n,z

I have also participated in a huge number of code reviews. https://review.openstack.org/#q,status:merged+reviewer:vishvananda%2540gmail.com,n,z

Primarily I have been spending time trying to get everything stabilized and cleaned up so that nova is production-ready in essex.

2a. What are the most pressing/important issues facing OpenStack as a whole?

OpenStack is old enough now that large entities are starting to deploy it in earnest. Now it is about ramping up adoption so it is ubiquitous. People who are wanting to use openstack should be concered

  • Deployability

This is still the most

  • Consistency between projects
  • Federation and bursting

2b. What are the most pressing/important issues facing your project?

There are two classes of issues facing nova. The first class includes issues that face operators and deployers. These are important to keep in mind because they drive code requirements.

  This is primarily a documentation effort, but also includes improving admin-apis and tooling
  Larger scale testing and QA will help here. Some re-architecting around no
 This is a larger issue that we will be facing over the next year.  Nova needs some re-architecting to improve
 security.  We need to address this a in phases, but it is probably the most important "Feature"
 Federation is one of the selling points of openstack, but this area needs specific focus if we are ever going to
 move virtual machines between clouds easily

The second class of issues are code related issues.

 Various efforts are underway to decrease the surface area of Nova. The subteam strategy we implemented during
 essex was only successful in a few cases. A plan has been formed around splitting nova-volume into its own project.
 The replacement of nova-network with quantum/melange that is planned over the next year should similarly isolate
 nova-network. The suggestion of specific  
 Componentizing different parts of the code base should help with this. 

3. What is your relationship to OpenStack & why is its success important to you and/or your company?

Links