Date and Time
: PDT 8:00am / UTC 15:00, Friday July 10, 2015Chair
: Bin Hu (AT&T)Participants
:Bin suggested to participate in B Release. We have completed our IPv6 Use Case and Gap Analysis with Kilo. We just reached our 1st milestone of creating a snapshot image of using a service VM as IPv6 vRouter with SLAAC internal interface. The snapshot image can be used as an IPv6-Router-VM and it automatically starts the necessary service on boot-up. This snapshot image can be integrated into B release as our minimum deliverables of IPv6 project, with necessary documentation and optionally test methodology if any. Further enhancement of this IPv6 snapshot image may be available for B release timeframe such as added security features, and metadata approach for initiating a cloud image.
Bin will draft our answers to Debra, and share with core members. Once Bin gets feedback, Bin will give the information to Debra on Monday.
The same before
Mark and Sridhar worked together, and reached our 1st milestone of creating a snapshot image of using a service VM as IPv6 vRouter with SLAAC internal interface. The snapshot image can be used as an IPv6-Router-VM and it automatically starts the necessary service on boot-up. This snapshot image can be integrated into B release as our minimum deliverables of IPv6 project, with necessary documentation and optionally test methodology if any. Further enhancement of this IPv6 snapshot image may be available for B release timeframe such as added security features, and metadata approach for initiating a cloud image.
In terms of SLAAC and DHCPv6 support, SLAAC is a must-have, and DHCPv6 is a nice-to-have.
Next Steps:
- Sridhar will finish documentation early next week and share with the community so that everyone can experiment and give feedback
- Sridhar and Mark will look into metadata approach to initiate a cloud image
Meeting adjourned.