cinder, ironic, tripleO, neutron, nova, keystone, glance, products, requirements, architecture, HPC
Arkady has been a member of OpenStack since Grizzly. He is director of engineering leading a team of developers responsible for development of DellEMC OpenStack solutions. Arkady has PhD. in CS from UIUC. He straddled academic, research, architect, developer, and product owner roles. Arkady roles included but not limited to, research publications and Program committee member for various conferences like FAST (https://www.usenix.org/legacy/events/fast11/organizers.html), Chair or board member of several standard activities, like DAT (http://www.datcollaborative.org), OpenFabric (https://www.openfabrics.org/index.php) and MPI-RT (http://www.cse.msstate.edu/~yogi/dandass-mpirt-2004.pdf) to product delivery, like EMC Atmos, Dell OpenStack solutions among others.
Arkady is passionate advocate of OpenStack and making its usage easier for users and administrators. He concentrates efforts of his team on extending OpenStack capabilities for enterprise use cases, from automatic deployment, and robustness, to HA, upgrade, extensibility and validation, to workload optimizations.
I'm involved in the following OpenStack projects: Cinder,Heat,Ironic,QA,Deployment
I am engineering lead in charge of DellEMC openstack solutions, representing Dell, DellEMC, VMware, Pivotal, VirtuStream and other parts of Dell Technologies. I am driving a team of pationate developers to improve quality, long term support, optmization for various workloads and ability to maintain solution as a customer private cloud over long period of time. I am activelly driving DellEMC participation of extended CI and distros CI to ensure consistent Customer experience.
My personal pashion is to extend interoperability and performance results so it is usable and reproducible to end Customers. I am working within refstack, defcore, rally and product working groups driving toward it.
I had been a board member of OpenFabrics, DAT Collaborative, MPI and several other open source organization, driving their adoption, legal framework, and continues development. The key is collaboration toward common goals of success of oragnization while responding to unique needs of individual groups. My biggest success was transition of DAT collaborative to OpenFarnrics and inclusion its code base into Linux.
The role of the board to setup a clear rules of engagements that can stand long period of time to provide stability for Customers, administrarors, and developers. Clear guidance allows clear definition what OpenStack is and what it is not, allows us to adopt to new technologies and new opportunities. It also allows us to make it clear where openstack ends so vendor companies can develop their own differentation to provide vibrant openstack ecosystem.
First and for most, clarity. There are too many chnages happening too quickly in haphazard matter that does not promote OpenStack goals of adoption. The consistency of rules across all projects to make pieces of the whole and joint solution rather then independent but incomplete deliverables.
One of the key needs for OpenStack is to provide guidance and support for transitioning of customer applications from baremetal and virtual environment to microservices architecture.
Stability and consistency of OpenStack as IaaS platform so customers can adopti it and optimize it for various workloads, beyond NFV and cloud native apps.